Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56c674861c6594a196d61ed95f53cd2b5e9f9a6deef9f48f608de456272d1a63

Tx prefix hash: ce6557d479598e572951decdf0946502427f5c4aa1a84f90480235a5597c514a
Tx public key: 13321bda03a2a36c3c4c4d7b9af19ff6cdaf34f086b60d6d0ffc3a734d45168e
Timestamp: 1765995210 Timestamp [UCT]: 2025-12-17 18:13:30 Age [y:d:h:m:s]: 00:006:02:01:46
Block: 1435737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4357 RingCT/type: yes/0
Extra: 0113321bda03a2a36c3c4c4d7b9af19ff6cdaf34f086b60d6d0ffc3a734d45168e0211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6262314f97b44d5b4f8912af9639ab17bf2ff631ee864723909c8412a42ab6f 0.600000000000 1924536 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": 1435747, "vin": [ { "gen": { "height": 1435737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6262314f97b44d5b4f8912af9639ab17bf2ff631ee864723909c8412a42ab6f" } } ], "extra": [ 1, 19, 50, 27, 218, 3, 162, 163, 108, 60, 76, 77, 123, 154, 241, 159, 246, 205, 175, 52, 240, 134, 182, 13, 109, 15, 252, 58, 115, 77, 69, 22, 142, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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