Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 311944a2533b4ca994a0072955182a8c8eea9aaa0e47937ce834441f1c076415

Tx prefix hash: ca5bb7421c891289d36ec4043a4b30304da3097b2eb8b418a8b8807a4b7f646e
Tx public key: 901a0861da9a7d38d1c3c675ab5a86e5bf336c8a0dc9d0f3d8214a66ec958b20
Timestamp: 1700802251 Timestamp [UCT]: 2023-11-24 05:04:11 Age [y:d:h:m:s]: 01:166:11:22:11
Block: 898389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380164 RingCT/type: yes/0
Extra: 01901a0861da9a7d38d1c3c675ab5a86e5bf336c8a0dc9d0f3d8214a66ec958b20021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.647536554000 dcy

stealth address amount amount idx
00: c8274ae8509e9af512affe9dfdd93cb3ba289990afe348e1f21b83a4c4242144 0.647536554000 1354802 of 0

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": 898399, "vin": [ { "gen": { "height": 898389 } } ], "vout": [ { "amount": 647536554, "target": { "key": "c8274ae8509e9af512affe9dfdd93cb3ba289990afe348e1f21b83a4c4242144" } } ], "extra": [ 1, 144, 26, 8, 97, 218, 154, 125, 56, 209, 195, 198, 117, 171, 90, 134, 229, 191, 51, 108, 138, 13, 201, 208, 243, 216, 33, 74, 102, 236, 149, 139, 32, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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