Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad716a0579a6d5f0ebb0720c444a5fea7d0021144721716b75214e9eeb43db0c

Tx prefix hash: f378a29f093ba3d927b81cdee7120fba6db694104ad5b69289cb4b6df216e9c2
Tx public key: d16f356664ceca896cf583a251f49be548504c20a94cb037af224d3860cd66a7
Timestamp: 1722636847 Timestamp [UCT]: 2024-08-02 22:14:07 Age [y:d:h:m:s]: 00:160:14:05:37
Block: 1079410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114890 RingCT/type: yes/0
Extra: 01d16f356664ceca896cf583a251f49be548504c20a94cb037af224d3860cd66a702110000001591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdd87f34c69eaf0c1efebb7ccd40c7acb8181aaeea615eb5f4a416459710e037 0.600000000000 1552353 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": 1079420, "vin": [ { "gen": { "height": 1079410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdd87f34c69eaf0c1efebb7ccd40c7acb8181aaeea615eb5f4a416459710e037" } } ], "extra": [ 1, 209, 111, 53, 102, 100, 206, 202, 137, 108, 245, 131, 162, 81, 244, 155, 229, 72, 80, 76, 32, 169, 76, 176, 55, 175, 34, 77, 56, 96, 205, 102, 167, 2, 17, 0, 0, 0, 21, 145, 225, 60, 4, 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