Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7d0f6b34951dabf2765ea02ff917157cbdb501137ab8ef9a8899ad41a185c56f

Tx prefix hash: d00d409b9a03b492f539b45c0b4b5f1a4cafe3d447bbe6c07635bc788a4f5fed
Tx public key: e51a676c83d8904144a816ed16bca3efc0f789b6bd60912f227483a92f408ae0
Timestamp: 1672058698 Timestamp [UCT]: 2022-12-26 12:44:58 Age [y:d:h:m:s]: 02:102:09:38:55
Block: 660988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594847 RingCT/type: yes/0
Extra: 01e51a676c83d8904144a816ed16bca3efc0f789b6bd60912f227483a92f408ae0021100000003e7ace25d000000000000000000

1 output(s) for total of 3.961615637000 dcy

stealth address amount amount idx
00: 9e668f32c3bfc5e835772bcb8f52800bbb3f474d09470ccc37c124214fe9f5a0 3.961615637000 1101737 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 660998, "vin": [ { "gen": { "height": 660988 } } ], "vout": [ { "amount": 3961615637, "target": { "key": "9e668f32c3bfc5e835772bcb8f52800bbb3f474d09470ccc37c124214fe9f5a0" } } ], "extra": [ 1, 229, 26, 103, 108, 131, 216, 144, 65, 68, 168, 22, 237, 22, 188, 163, 239, 192, 247, 137, 182, 189, 96, 145, 47, 34, 116, 131, 169, 47, 64, 138, 224, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8