Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 320a94e4e5d38f61b401e11a7cd733f3a39e4f769054e5c0fcdc05f7fb8f7b2c

Tx prefix hash: f0438642af1bec66bc55ab464df2052ec4e80c4992b2e7835b1ff8f4e22ff7fd
Tx public key: 337377ace8d878ae80f176ba32a323c06258fd322931bfea93f60bdea0dce1bf
Timestamp: 1762704451 Timestamp [UCT]: 2025-11-09 16:07:31 Age [y:d:h:m:s]: 00:046:18:48:52
Block: 1408474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33496 RingCT/type: yes/0
Extra: 01337377ace8d878ae80f176ba32a323c06258fd322931bfea93f60bdea0dce1bf02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a08f06274067a6b234bcff57a1e92cfb293938bbeafabee2947fecf18d58d30 0.600000000000 1896903 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": 1408484, "vin": [ { "gen": { "height": 1408474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a08f06274067a6b234bcff57a1e92cfb293938bbeafabee2947fecf18d58d30" } } ], "extra": [ 1, 51, 115, 119, 172, 232, 216, 120, 174, 128, 241, 118, 186, 50, 163, 35, 192, 98, 88, 253, 50, 41, 49, 191, 234, 147, 246, 11, 222, 160, 220, 225, 191, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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