Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1ea9b1513def50ca3ca0f321476f9b658f9d3a758068af1b0ea7d0cac1625a8

Tx prefix hash: f1c2246730819cf1fcaa218ece3ba9edf51f4fed5b9e3327f6c33f355ea580a3
Tx public key: 1c2fd6836f1b926f30b88901a8e86d96bb2451442f605af334331c8e7d752fae
Timestamp: 1761474189 Timestamp [UCT]: 2025-10-26 10:23:09 Age [y:d:h:m:s]: 00:074:09:28:00
Block: 1398284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53271 RingCT/type: yes/0
Extra: 011c2fd6836f1b926f30b88901a8e86d96bb2451442f605af334331c8e7d752fae02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b799125201f8ea26a7adeaca28e0ea9e560d3a2a17fafb4fb1b0e6eb96e4ac3e 0.600000000000 1886579 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": 1398294, "vin": [ { "gen": { "height": 1398284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b799125201f8ea26a7adeaca28e0ea9e560d3a2a17fafb4fb1b0e6eb96e4ac3e" } } ], "extra": [ 1, 28, 47, 214, 131, 111, 27, 146, 111, 48, 184, 137, 1, 168, 232, 109, 150, 187, 36, 81, 68, 47, 96, 90, 243, 52, 51, 28, 142, 125, 117, 47, 174, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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