Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44a0c97348d43f304f458b3b21162e5bb3863a6828c4524dfa8cb457282d3919

Tx prefix hash: d36fed9680531888601ea89bd5a3c3b591da0e5a84d6794de31b05cb6c4d50ff
Tx public key: d6da22479b2053b52fdc3d872d3341cf1410894a9cf6a936c09b339d4c3d1702
Timestamp: 1722758117 Timestamp [UCT]: 2024-08-04 07:55:17 Age [y:d:h:m:s]: 00:204:04:07:59
Block: 1080413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145789 RingCT/type: yes/0
Extra: 01d6da22479b2053b52fdc3d872d3341cf1410894a9cf6a936c09b339d4c3d1702021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ab16cf185906e6bf901cee462d0ab7f0d436c84e20c8b884545582fc80e7d1b 0.600000000000 1553760 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": 1080423, "vin": [ { "gen": { "height": 1080413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ab16cf185906e6bf901cee462d0ab7f0d436c84e20c8b884545582fc80e7d1b" } } ], "extra": [ 1, 214, 218, 34, 71, 155, 32, 83, 181, 47, 220, 61, 135, 45, 51, 65, 207, 20, 16, 137, 74, 156, 246, 169, 54, 192, 155, 51, 157, 76, 61, 23, 2, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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