Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c95f85f6680ad22b5efc1701afc1bbc3fa25ac0990938c54967de91df076037

Tx prefix hash: 378ea0a2351ab156c2b08244290c70f4daee384b5ed39e956ebd2f6fd7759820
Tx public key: e7355bd2b5701f4f68818d18d07286ba9fe5152b9d8fab2271c34a45b4c9976b
Timestamp: 1711803133 Timestamp [UCT]: 2024-03-30 12:52:13 Age [y:d:h:m:s]: 01:045:07:30:44
Block: 989620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293360 RingCT/type: yes/0
Extra: 01e7355bd2b5701f4f68818d18d07286ba9fe5152b9d8fab2271c34a45b4c9976b0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d67c36da08c1ec5e6b47f0f522a9f6381d0498ba98595a16d293472421bb51f 0.600000000000 1449923 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": 989630, "vin": [ { "gen": { "height": 989620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d67c36da08c1ec5e6b47f0f522a9f6381d0498ba98595a16d293472421bb51f" } } ], "extra": [ 1, 231, 53, 91, 210, 181, 112, 31, 79, 104, 129, 141, 24, 208, 114, 134, 186, 159, 229, 21, 43, 157, 143, 171, 34, 113, 195, 74, 69, 180, 201, 151, 107, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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