Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fffd636a2906f4c4d70e890fa1c4fb485a041d42e5877f65f5bcd6d62cdaf71

Tx prefix hash: ad6a620340927f1d5b10cbf51f0f1e5a6b602be309d2f79023f3f45afec8a830
Tx public key: 76c7a3a3f6d3c3597f6abe1ac7d6b8c631456976e8a7af98d250f381949528a5
Timestamp: 1712362461 Timestamp [UCT]: 2024-04-06 00:14:21 Age [y:d:h:m:s]: 00:325:19:27:48
Block: 994197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232955 RingCT/type: yes/0
Extra: 0176c7a3a3f6d3c3597f6abe1ac7d6b8c631456976e8a7af98d250f381949528a502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcb1d81004a19bfe28facaa2827d87662bf3732723d904aa75619b5e12031713 0.600000000000 1454599 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": 994207, "vin": [ { "gen": { "height": 994197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcb1d81004a19bfe28facaa2827d87662bf3732723d904aa75619b5e12031713" } } ], "extra": [ 1, 118, 199, 163, 163, 246, 211, 195, 89, 127, 106, 190, 26, 199, 214, 184, 198, 49, 69, 105, 118, 232, 167, 175, 152, 210, 80, 243, 129, 148, 149, 40, 165, 2, 17, 0, 0, 0, 2, 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