Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241d42b669901ef144a2a9cbab28aab4b99fa46f1e489f77bf4f2e11233da323

Tx prefix hash: 89d212203ca168978fb1423863fbd5009ec46c727984ea18a1c916c760fafe83
Tx public key: 57ae1b28c111004d8def1c1d5ce95c9c1b67a0264f0ff5dacf72e111231ab913
Timestamp: 1751281309 Timestamp [UCT]: 2025-06-30 11:01:49 Age [y:d:h:m:s]: 00:143:09:31:14
Block: 1315794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100677 RingCT/type: yes/0
Extra: 0157ae1b28c111004d8def1c1d5ce95c9c1b67a0264f0ff5dacf72e111231ab913021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc99b1e36acc77d5dd922c5cc4253989363fd39a5024a1e4481b26f1a20a3a7e 0.600000000000 1803451 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": 1315804, "vin": [ { "gen": { "height": 1315794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc99b1e36acc77d5dd922c5cc4253989363fd39a5024a1e4481b26f1a20a3a7e" } } ], "extra": [ 1, 87, 174, 27, 40, 193, 17, 0, 77, 141, 239, 28, 29, 92, 233, 92, 156, 27, 103, 160, 38, 79, 15, 245, 218, 207, 114, 225, 17, 35, 26, 185, 19, 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