Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c996ee7b73079780230ac47edf344afdcd1c263ed39edc1f65b7c32d7e98a271

Tx prefix hash: 72b82659d576697a94a519640553c6164aba24c881bb88d5b7ef982c4bc037fc
Tx public key: d9ec624973b971461d2c5e7b2ca99be8f24c8aadd284a522d8e66b1443c30d2d
Timestamp: 1725727858 Timestamp [UCT]: 2024-09-07 16:50:58 Age [y:d:h:m:s]: 00:077:14:35:10
Block: 1105054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55481 RingCT/type: yes/0
Extra: 01d9ec624973b971461d2c5e7b2ca99be8f24c8aadd284a522d8e66b1443c30d2d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d97265754967135bd87af98f27bc74bed032ae7d346d3d0ef2943238953c544e 0.600000000000 1582391 of 15

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": 1105064, "vin": [ { "gen": { "height": 1105054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d97265754967135bd87af98f27bc74bed032ae7d346d3d0ef2943238953c544e" } } ], "extra": [ 1, 217, 236, 98, 73, 115, 185, 113, 70, 29, 44, 94, 123, 44, 169, 155, 232, 242, 76, 138, 173, 210, 132, 165, 34, 216, 230, 107, 20, 67, 195, 13, 45, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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