Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0489c19874295d3c8d6e8c404fef9e9a9280461f51e7d7e1b45ef9fa528d9eb

Tx prefix hash: c65f97c1a1e67d1c44be4b448c47f39d8261e29d913eaf625199e35f31246e70
Tx public key: 57bb0b66f83c0153f8e5a2356f7aea3ddda0c424a97355dd98d61c433ec90d2d
Timestamp: 1714303732 Timestamp [UCT]: 2024-04-28 11:28:52 Age [y:d:h:m:s]: 00:200:15:36:33
Block: 1010324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143630 RingCT/type: yes/0
Extra: 0157bb0b66f83c0153f8e5a2356f7aea3ddda0c424a97355dd98d61c433ec90d2d02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 088efcf0b35a324604303f40ab08c9acab54d5251296c6dc2832ed89df3f7e6c 0.600000000000 1472246 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": 1010334, "vin": [ { "gen": { "height": 1010324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "088efcf0b35a324604303f40ab08c9acab54d5251296c6dc2832ed89df3f7e6c" } } ], "extra": [ 1, 87, 187, 11, 102, 248, 60, 1, 83, 248, 229, 162, 53, 111, 122, 234, 61, 221, 160, 196, 36, 169, 115, 85, 221, 152, 214, 28, 67, 62, 201, 13, 45, 2, 17, 0, 0, 0, 5, 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