Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16f7fdaf29383f3a4a360c8eeab9f5fad11834fd151dcc8dc63f3687d403766c

Tx prefix hash: 9d11a3b66973bc799d88eca94382e05e6aeb3e1a6fddb4fd7b7fbaf18b638453
Tx public key: 49d8b7db540f65445a78e371715de4e8c2151d1e6d40948fb1538702d2eac762
Timestamp: 1718075602 Timestamp [UCT]: 2024-06-11 03:13:22 Age [y:d:h:m:s]: 00:213:16:57:55
Block: 1041612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152931 RingCT/type: yes/0
Extra: 0149d8b7db540f65445a78e371715de4e8c2151d1e6d40948fb1538702d2eac76202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e11e5c4fc7ccfe8dbe1637ec479043b0a501dca5cb4c03c0839f3a9fa6d39002 0.600000000000 1510329 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": 1041622, "vin": [ { "gen": { "height": 1041612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e11e5c4fc7ccfe8dbe1637ec479043b0a501dca5cb4c03c0839f3a9fa6d39002" } } ], "extra": [ 1, 73, 216, 183, 219, 84, 15, 101, 68, 90, 120, 227, 113, 113, 93, 228, 232, 194, 21, 29, 30, 109, 64, 148, 143, 177, 83, 135, 2, 210, 234, 199, 98, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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