Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 251328f483d7c2c811733c9c9e069e4cbf78ab8efde5e3dfc2aae8583455d2f7

Tx prefix hash: d458ab84fad2b3ce2652153ed123146285acd33df3ab9c1533496270a2e7d90d
Tx public key: 4b3fc03984bcc37e9f4acb0e11a93309e8749234734c26b45260b7a8c25efd26
Timestamp: 1749686768 Timestamp [UCT]: 2025-06-12 00:06:08 Age [y:d:h:m:s]: 00:157:22:15:43
Block: 1303084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110588 RingCT/type: yes/0
Extra: 014b3fc03984bcc37e9f4acb0e11a93309e8749234734c26b45260b7a8c25efd26021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f7cee6530d29698a017d7bf4cf12e3b49ecd16ca6766974dbff84599966bfcc 0.600000000000 1790659 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": 1303094, "vin": [ { "gen": { "height": 1303084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f7cee6530d29698a017d7bf4cf12e3b49ecd16ca6766974dbff84599966bfcc" } } ], "extra": [ 1, 75, 63, 192, 57, 132, 188, 195, 126, 159, 74, 203, 14, 17, 169, 51, 9, 232, 116, 146, 52, 115, 76, 38, 180, 82, 96, 183, 168, 194, 94, 253, 38, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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