Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4498db27b1c6b9ecb8222fe0d884efbdb6d9ae370b5f6e4fb6e118ee7187ff8a

Tx prefix hash: f604288fb6343881a71dbc8a3a5b10ca68aeb05a0e76c67960d47517ca397e5e
Tx public key: 4bac6de00ed6e8c71c03a96efdeb606251f2cb4637cbb5ab1b4880d74134a791
Timestamp: 1712528782 Timestamp [UCT]: 2024-04-07 22:26:22 Age [y:d:h:m:s]: 00:350:16:15:34
Block: 995580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250743 RingCT/type: yes/0
Extra: 014bac6de00ed6e8c71c03a96efdeb606251f2cb4637cbb5ab1b4880d74134a79102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98afc4bd07a734b81772cc2d8f017ea33efb1508a1edb61ae313960d01bac1ec 0.600000000000 1455990 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": 995590, "vin": [ { "gen": { "height": 995580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98afc4bd07a734b81772cc2d8f017ea33efb1508a1edb61ae313960d01bac1ec" } } ], "extra": [ 1, 75, 172, 109, 224, 14, 214, 232, 199, 28, 3, 169, 110, 253, 235, 96, 98, 81, 242, 203, 70, 55, 203, 181, 171, 27, 72, 128, 215, 65, 52, 167, 145, 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