Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c4c51a7ea970e2b036670a416e411470c7f1bf0ee2d3ad35d37a31e1c4d9ef

Tx prefix hash: 96f74888ebdc45b57dbd518291784c71bc9996b425b13f0d5738a28fbffd35a3
Tx public key: b122e6b85ab5c1cbf5057aed25709a2b7a3f627c4eef1175113e92d9e201ec6a
Timestamp: 1746035664 Timestamp [UCT]: 2025-04-30 17:54:24 Age [y:d:h:m:s]: 00:241:20:42:53
Block: 1272883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170632 RingCT/type: yes/0
Extra: 01b122e6b85ab5c1cbf5057aed25709a2b7a3f627c4eef1175113e92d9e201ec6a021100000006d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ba3444cb63568a0a1319aeec8aebf8995a77c836df92fd360ff05e7ee2c277b 0.600000000000 1760160 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": 1272893, "vin": [ { "gen": { "height": 1272883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ba3444cb63568a0a1319aeec8aebf8995a77c836df92fd360ff05e7ee2c277b" } } ], "extra": [ 1, 177, 34, 230, 184, 90, 181, 193, 203, 245, 5, 122, 237, 37, 112, 154, 43, 122, 63, 98, 124, 78, 239, 17, 117, 17, 62, 146, 217, 226, 1, 236, 106, 2, 17, 0, 0, 0, 6, 216, 231, 210, 65, 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