Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b58bddc8ff50f5042b3b985450f8430b2d9cfb936801711afad8e2caf87ae608

Tx prefix hash: d5d27110d617950bd95e88e3b29c2d26530f1f81d705fe1f0a0cc98dade6d8de
Tx public key: 3643eaa29293d181b926012af91cd5588ea7efcce118e3f7e23bc92c9407de90
Timestamp: 1712822267 Timestamp [UCT]: 2024-04-11 07:57:47 Age [y:d:h:m:s]: 00:320:09:55:54
Block: 998020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229074 RingCT/type: yes/0
Extra: 013643eaa29293d181b926012af91cd5588ea7efcce118e3f7e23bc92c9407de9002110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d95bba1a58301803e7fb8016ba0796dff020244d1bab7069281aefd5bf78f3f2 0.600000000000 1458454 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": 998030, "vin": [ { "gen": { "height": 998020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d95bba1a58301803e7fb8016ba0796dff020244d1bab7069281aefd5bf78f3f2" } } ], "extra": [ 1, 54, 67, 234, 162, 146, 147, 209, 129, 185, 38, 1, 42, 249, 28, 213, 88, 142, 167, 239, 204, 225, 24, 227, 247, 226, 59, 201, 44, 148, 7, 222, 144, 2, 17, 0, 0, 0, 14, 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