Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40bcdb38275ccdfdd54abaa80851520e0035033932ae3dd3d86b015dfe37742e

Tx prefix hash: 7f77768388cc37e123f1e3e73d03ab4d9e802dcdb6cfd1ab9ebcd99eaa922afd
Tx public key: cd6ee1e0af031a41d503079eff15afb0c1c7d9b758f189928cf8e07ee8e66615
Timestamp: 1713729162 Timestamp [UCT]: 2024-04-21 19:52:42 Age [y:d:h:m:s]: 00:344:01:23:33
Block: 1005556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245963 RingCT/type: yes/0
Extra: 01cd6ee1e0af031a41d503079eff15afb0c1c7d9b758f189928cf8e07ee8e666150211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a25776e13b97604eae97d756c6e7c87fd1f0fa2cde00cd7e1ff4cad100eb2d77 0.600000000000 1466286 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": 1005566, "vin": [ { "gen": { "height": 1005556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a25776e13b97604eae97d756c6e7c87fd1f0fa2cde00cd7e1ff4cad100eb2d77" } } ], "extra": [ 1, 205, 110, 225, 224, 175, 3, 26, 65, 213, 3, 7, 158, 255, 21, 175, 176, 193, 199, 217, 183, 88, 241, 137, 146, 140, 248, 224, 126, 232, 230, 102, 21, 2, 17, 0, 0, 0, 3, 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