Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb56cbe581254c160925e25d40ff62b6020a1658e7aeeae484d5d7f308db87f1

Tx prefix hash: 053bdb2e63be3b672f08d3466a95b22d65c7f6ee15fb068d7b203fa8e7898764
Tx public key: dfe1fd35c579482485e7f626323d4c911b121e35b31a56ba0b891d361a729607
Timestamp: 1723307691 Timestamp [UCT]: 2024-08-10 16:34:51 Age [y:d:h:m:s]: 00:245:04:38:28
Block: 1084976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175122 RingCT/type: yes/0
Extra: 01dfe1fd35c579482485e7f626323d4c911b121e35b31a56ba0b891d361a72960702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a42208a569f48c877fd2ea47a22870ae012ac412c62a2d23ca25a70680006f0 0.600000000000 1559443 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": 1084986, "vin": [ { "gen": { "height": 1084976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a42208a569f48c877fd2ea47a22870ae012ac412c62a2d23ca25a70680006f0" } } ], "extra": [ 1, 223, 225, 253, 53, 197, 121, 72, 36, 133, 231, 246, 38, 50, 61, 76, 145, 27, 18, 30, 53, 179, 26, 86, 186, 11, 137, 29, 54, 26, 114, 150, 7, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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