Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0572422bb7e0dd7c03bde9fd48bcde2d40e0d12dc74be0860756c21e0014289

Tx prefix hash: 33334a7704e1b54dcf21a6be1991a1887f2e33ab48a938d58c837db2728c51f2
Tx public key: d66b5e3978e7f03dc04a4c120a8def55424cd132896dc179f96f5199830a2ae1
Timestamp: 1709981977 Timestamp [UCT]: 2024-03-09 10:59:37 Age [y:d:h:m:s]: 01:038:11:07:26
Block: 974515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288481 RingCT/type: yes/0
Extra: 01d66b5e3978e7f03dc04a4c120a8def55424cd132896dc179f96f5199830a2ae102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18a3811617ad4726cc7fcd5f9f164223d6e9d0e14a3b430921cc6cad9fc9e059 0.600000000000 1434474 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": 974525, "vin": [ { "gen": { "height": 974515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18a3811617ad4726cc7fcd5f9f164223d6e9d0e14a3b430921cc6cad9fc9e059" } } ], "extra": [ 1, 214, 107, 94, 57, 120, 231, 240, 61, 192, 74, 76, 18, 10, 141, 239, 85, 66, 76, 209, 50, 137, 109, 193, 121, 249, 111, 81, 153, 131, 10, 42, 225, 2, 17, 0, 0, 0, 1, 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