Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 603e48df7cf00d229a4167bd553e1d0eaff54df1422d5747d7bff0715bb00c42

Tx prefix hash: 9a2c2a78353ec1c51580097c86510a736220a72a946afed10158492e1d4a6401
Tx public key: e061e14fc403701df43e2339c806e4ca64a0ca794f3d5b4b0294fb756c6b706c
Timestamp: 1759955190 Timestamp [UCT]: 2025-10-08 20:26:30 Age [y:d:h:m:s]: 00:038:23:01:53
Block: 1385680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27903 RingCT/type: yes/0
Extra: 01e061e14fc403701df43e2339c806e4ca64a0ca794f3d5b4b0294fb756c6b706c02110000000797baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8798c9ca37475551282758a39e3354e27b511da5551fe2b027b95d58692553ac 0.600000000000 1873843 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": 1385690, "vin": [ { "gen": { "height": 1385680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8798c9ca37475551282758a39e3354e27b511da5551fe2b027b95d58692553ac" } } ], "extra": [ 1, 224, 97, 225, 79, 196, 3, 112, 29, 244, 62, 35, 57, 200, 6, 228, 202, 100, 160, 202, 121, 79, 61, 91, 75, 2, 148, 251, 117, 108, 107, 112, 108, 2, 17, 0, 0, 0, 7, 151, 186, 249, 34, 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