Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2521600cf0bec3824e3c545f9a160b3442d3b7dcf8525ab91feb413e316e4cc

Tx prefix hash: 014716440fef358ce1ad49ce8babbe14c3e64c204b435a22c28cbc40bc009f9b
Tx public key: af8211a6bbeed450968c1075f59c0fa70a5c40e048872fb5551e1b9f7ce9dbc9
Timestamp: 1737617871 Timestamp [UCT]: 2025-01-23 07:37:51 Age [y:d:h:m:s]: 00:145:12:09:21
Block: 1203423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103730 RingCT/type: yes/0
Extra: 01af8211a6bbeed450968c1075f59c0fa70a5c40e048872fb5551e1b9f7ce9dbc9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3ed8753c38b86d60d110ac8b8aa3c774c3cf0e3b4c1954816c87196fe8192f7 0.600000000000 1690100 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": 1203433, "vin": [ { "gen": { "height": 1203423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3ed8753c38b86d60d110ac8b8aa3c774c3cf0e3b4c1954816c87196fe8192f7" } } ], "extra": [ 1, 175, 130, 17, 166, 187, 238, 212, 80, 150, 140, 16, 117, 245, 156, 15, 167, 10, 92, 64, 224, 72, 135, 47, 181, 85, 30, 27, 159, 124, 233, 219, 201, 2, 17, 0, 0, 0, 3, 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