Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23d0ab0600feb893f7619bfd64eb11f0daeb2b941d1c2da003c43a804694ed4f

Tx prefix hash: 39486fde2076be985c50f8ea1efe5af2322104208d30a4b071384fa9f81f8350
Tx public key: 90a5c30815fddd4b0b73fd5ae4ba9bdc72a174b7b6cc16cf720c6620e189c07e
Timestamp: 1732951442 Timestamp [UCT]: 2024-11-30 07:24:02 Age [y:d:h:m:s]: 00:125:00:24:17
Block: 1164831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89150 RingCT/type: yes/0
Extra: 0190a5c30815fddd4b0b73fd5ae4ba9bdc72a174b7b6cc16cf720c6620e189c07e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dddbb71aa215299cd2677d62f8896f77e86630b3ee93227bf3b5c3052518143f 0.600000000000 1650506 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": 1164841, "vin": [ { "gen": { "height": 1164831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dddbb71aa215299cd2677d62f8896f77e86630b3ee93227bf3b5c3052518143f" } } ], "extra": [ 1, 144, 165, 195, 8, 21, 253, 221, 75, 11, 115, 253, 90, 228, 186, 155, 220, 114, 161, 116, 183, 182, 204, 22, 207, 114, 12, 102, 32, 225, 137, 192, 126, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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