Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6187c095234b96549d33355c77ee3cc184ffeb73b9301feed533b0ed1bfdfcd2

Tx prefix hash: 20716d444f6303c05f7b4ad4d9aa4cee2da2d86bec2ab1ace12dd853d0b7eef9
Tx public key: 0b917517fa88698470f3c4a8a022486e32c3c714a8e21dd3dbb5ecb90fa6fc64
Timestamp: 1737528776 Timestamp [UCT]: 2025-01-22 06:52:56 Age [y:d:h:m:s]: 00:149:01:05:30
Block: 1202683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106233 RingCT/type: yes/0
Extra: 010b917517fa88698470f3c4a8a022486e32c3c714a8e21dd3dbb5ecb90fa6fc64021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cda6f6cf58aa4662a12e0eb4ce7da27a84c3e7fe924720ecdabff3ca729d0975 0.600000000000 1689348 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": 1202693, "vin": [ { "gen": { "height": 1202683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cda6f6cf58aa4662a12e0eb4ce7da27a84c3e7fe924720ecdabff3ca729d0975" } } ], "extra": [ 1, 11, 145, 117, 23, 250, 136, 105, 132, 112, 243, 196, 168, 160, 34, 72, 110, 50, 195, 199, 20, 168, 226, 29, 211, 219, 181, 236, 185, 15, 166, 252, 100, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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