Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dab2059fcf1c2281bd1bc67432be8a6f56c7faa962005a60b0372f4b7fd580c7

Tx prefix hash: 3cf8c64ebd10f84997734cdd733925946ecd4b6a3c7620e011ce0d14076e7cf2
Tx public key: b48b7475cc0a0c9f1fb1ec578c6ff1bcce95ed7148a65a01ec72cf1cdd4599fb
Timestamp: 1734337323 Timestamp [UCT]: 2024-12-16 08:22:03 Age [y:d:h:m:s]: 00:135:08:38:04
Block: 1176326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96526 RingCT/type: yes/0
Extra: 01b48b7475cc0a0c9f1fb1ec578c6ff1bcce95ed7148a65a01ec72cf1cdd4599fb021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 179c578a8e02cd4c6a8ae883971d65f76c2002510147db1aff98f763b95775c2 0.600000000000 1662657 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": 1176336, "vin": [ { "gen": { "height": 1176326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "179c578a8e02cd4c6a8ae883971d65f76c2002510147db1aff98f763b95775c2" } } ], "extra": [ 1, 180, 139, 116, 117, 204, 10, 12, 159, 31, 177, 236, 87, 140, 111, 241, 188, 206, 149, 237, 113, 72, 166, 90, 1, 236, 114, 207, 28, 221, 69, 153, 251, 2, 17, 0, 0, 0, 5, 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