Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50089a64a2379c67ca646f66be80e8c83e1047e15d927f1dfa3aa00e8c05dd78

Tx prefix hash: ccda01f57f3457101d2e78480e5e7f7b20b679efb4f9e3695619fc32ecb00cf1
Tx public key: 8ae39aca7051c453aa44a8dd0334fd6328b734cda0593baa615d52d3b902c9bd
Timestamp: 1718528998 Timestamp [UCT]: 2024-06-16 09:09:58 Age [y:d:h:m:s]: 00:131:08:14:20
Block: 1045378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94025 RingCT/type: yes/0
Extra: 018ae39aca7051c453aa44a8dd0334fd6328b734cda0593baa615d52d3b902c9bd0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8858647e6c6a6037f6c0937402e67d2f4151146a43ba371a77585e87c9d98b49 0.600000000000 1514931 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": 1045388, "vin": [ { "gen": { "height": 1045378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8858647e6c6a6037f6c0937402e67d2f4151146a43ba371a77585e87c9d98b49" } } ], "extra": [ 1, 138, 227, 154, 202, 112, 81, 196, 83, 170, 68, 168, 221, 3, 52, 253, 99, 40, 183, 52, 205, 160, 89, 59, 170, 97, 93, 82, 211, 185, 2, 201, 189, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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