Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db95519e4436701e171dee182c7fec880ffdafb6bc0b8787c00fbf084dcce5d5

Tx prefix hash: cb208aa2f36e151e81109f53e7abd29595c6a0c06e85254890fad3f2124ac531
Tx public key: 3c85b79ab3d7024e7914229f02e425c3fc4349aa7e32cdc7f014d4f2793e7883
Timestamp: 1702319838 Timestamp [UCT]: 2023-12-11 18:37:18 Age [y:d:h:m:s]: 01:133:13:20:18
Block: 910980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356598 RingCT/type: yes/0
Extra: 013c85b79ab3d7024e7914229f02e425c3fc4349aa7e32cdc7f014d4f2793e78830211000000034b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d73400261066a669af601dc596a1d436ba97a11b04b3a13800c5ac4c158fe7c 0.600000000000 1368155 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": 910990, "vin": [ { "gen": { "height": 910980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d73400261066a669af601dc596a1d436ba97a11b04b3a13800c5ac4c158fe7c" } } ], "extra": [ 1, 60, 133, 183, 154, 179, 215, 2, 78, 121, 20, 34, 159, 2, 228, 37, 195, 252, 67, 73, 170, 126, 50, 205, 199, 240, 20, 212, 242, 121, 62, 120, 131, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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