Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4761900d5d83045d742472e41569819445ec0709c3f4a1eb55864ac4dc82fe

Tx prefix hash: afbd6896394ca56a65ef8241fa989fd3ed4b3d8bc9b05440e0afe4ac04a5586b
Tx public key: e4ea4d78175fdbbf06157378e5dc476f01c925f9b57c999f5cb83f2d2cd9792a
Timestamp: 1712656920 Timestamp [UCT]: 2024-04-09 10:02:00 Age [y:d:h:m:s]: 01:207:17:48:56
Block: 996652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407152 RingCT/type: yes/0
Extra: 01e4ea4d78175fdbbf06157378e5dc476f01c925f9b57c999f5cb83f2d2cd9792a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb90902c4dea2292bd9d5f425cdb64023dbcde7f1d5a85c2f196a7de58123601 0.600000000000 1457078 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": 996662, "vin": [ { "gen": { "height": 996652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb90902c4dea2292bd9d5f425cdb64023dbcde7f1d5a85c2f196a7de58123601" } } ], "extra": [ 1, 228, 234, 77, 120, 23, 95, 219, 191, 6, 21, 115, 120, 229, 220, 71, 111, 1, 201, 37, 249, 181, 124, 153, 159, 92, 184, 63, 45, 44, 217, 121, 42, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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