Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c85c708f75663736057ef05de8ad607aaa4a25b17703e2b2dcd0110105c9f94a

Tx prefix hash: 4a44476a6e19bca6813ba6b99f0f15193caa21dcd99aec44d0e3e3d62fa2eadd
Tx public key: ae8d09e19b2dd89dee7f1c3fe208365561c8f886a31ee53f50d9ff1a508551f7
Timestamp: 1731484389 Timestamp [UCT]: 2024-11-13 07:53:09 Age [y:d:h:m:s]: 00:217:10:53:49
Block: 1152669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155158 RingCT/type: yes/0
Extra: 01ae8d09e19b2dd89dee7f1c3fe208365561c8f886a31ee53f50d9ff1a508551f70211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35225a868161692c8c072dc5fc4b0c68270c9a277dc65877eb81a8a08a84d6b6 0.600000000000 1638272 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": 1152679, "vin": [ { "gen": { "height": 1152669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35225a868161692c8c072dc5fc4b0c68270c9a277dc65877eb81a8a08a84d6b6" } } ], "extra": [ 1, 174, 141, 9, 225, 155, 45, 216, 157, 238, 127, 28, 63, 226, 8, 54, 85, 97, 200, 248, 134, 163, 30, 229, 63, 80, 217, 255, 26, 80, 133, 81, 247, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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