Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2129c8a4d212cbf35b85fe0f13fc09728122a0ecf64fb97081476d8d3bd2f0

Tx prefix hash: fc0aaabe2c90d5e220cc2e818f7aaa8b825e10fc026c867cb6743cc58bf2c8f5
Tx public key: 734580a67aafae6dc7670c661ee883dd1aad74ce17f046391cee2b47cfb0c971
Timestamp: 1754421901 Timestamp [UCT]: 2025-08-05 19:25:01 Age [y:d:h:m:s]: 00:009:23:33:59
Block: 1340977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6403 RingCT/type: yes/0
Extra: 01734580a67aafae6dc7670c661ee883dd1aad74ce17f046391cee2b47cfb0c9710211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e970ee78bd5a35bc341ea72d1f1503e818f14ec09e3a9f627f7301e8200e604e 0.600000000000 1828798 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": 1340987, "vin": [ { "gen": { "height": 1340977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e970ee78bd5a35bc341ea72d1f1503e818f14ec09e3a9f627f7301e8200e604e" } } ], "extra": [ 1, 115, 69, 128, 166, 122, 175, 174, 109, 199, 103, 12, 102, 30, 232, 131, 221, 26, 173, 116, 206, 23, 240, 70, 57, 28, 238, 43, 71, 207, 176, 201, 113, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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