Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a249cf4e14af0bf306a62db9a053b825ead42c934f89f295908bfbfed33f3cac

Tx prefix hash: a8d2cc8403782ad8464bb84e4d9e07577b8855c6e7905162e56417f58001b10c
Tx public key: e70b9405af2f2a928a00cae99f3ea5bc305447cd8798c57dab374651a8091b0c
Timestamp: 1750032520 Timestamp [UCT]: 2025-06-16 00:08:40 Age [y:d:h:m:s]: 00:227:17:52:06
Block: 1305871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160471 RingCT/type: yes/0
Extra: 01e70b9405af2f2a928a00cae99f3ea5bc305447cd8798c57dab374651a8091b0c02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ccf6814aa17b52a0622e5408de12e3dee8be53df7b84ea85e3256add9a96e16 0.600000000000 1793474 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": 1305881, "vin": [ { "gen": { "height": 1305871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ccf6814aa17b52a0622e5408de12e3dee8be53df7b84ea85e3256add9a96e16" } } ], "extra": [ 1, 231, 11, 148, 5, 175, 47, 42, 146, 138, 0, 202, 233, 159, 62, 165, 188, 48, 84, 71, 205, 135, 152, 197, 125, 171, 55, 70, 81, 168, 9, 27, 12, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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