Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bfd620bcc09ff382b9b295d34df63a760306ce02897679437b5a0b600206882

Tx prefix hash: 1b77b39d04864a96c32062c4ce5a1aa418f88b7185148082cdbd2430814e906d
Tx public key: e36e505ff8f4bae87a87f1e604c38f942c315fec0341c4d124f3cf4479c8ab57
Timestamp: 1750071728 Timestamp [UCT]: 2025-06-16 11:02:08 Age [y:d:h:m:s]: 00:148:22:13:05
Block: 1306186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104224 RingCT/type: yes/0
Extra: 01e36e505ff8f4bae87a87f1e604c38f942c315fec0341c4d124f3cf4479c8ab57021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56e2d30faa3887d3177d9eb72380563b3ec26702bf9e3c0b2b057942370f19ff 0.600000000000 1793789 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": 1306196, "vin": [ { "gen": { "height": 1306186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56e2d30faa3887d3177d9eb72380563b3ec26702bf9e3c0b2b057942370f19ff" } } ], "extra": [ 1, 227, 110, 80, 95, 248, 244, 186, 232, 122, 135, 241, 230, 4, 195, 143, 148, 44, 49, 95, 236, 3, 65, 196, 209, 36, 243, 207, 68, 121, 200, 171, 87, 2, 17, 0, 0, 0, 2, 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