Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baf40b6909581833a22ea10e53751c198aa96592998f4719bb82a2a8c649646d

Tx prefix hash: c1f4c56cd2ad7a63dae2be76f8247c462f8a72995192e5093975202e73247ae2
Tx public key: 608d81fba399cb0503b30555d61e4016950bf64d4d9972b010e3ae8f60f487fe
Timestamp: 1657349978 Timestamp [UCT]: 2022-07-09 06:59:38 Age [y:d:h:m:s]: 02:178:10:11:42
Block: 539867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 648859 RingCT/type: yes/0
Extra: 01608d81fba399cb0503b30555d61e4016950bf64d4d9972b010e3ae8f60f487fe02110000000d4da16a3a000000000000000000

1 output(s) for total of 9.981519664000 dcy

stealth address amount amount idx
00: 1f68514f97f013308cbd86f43b2a2cb70f933af2fc4c1a27cd19c9e95c2122e3 9.981519664000 970038 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": 539877, "vin": [ { "gen": { "height": 539867 } } ], "vout": [ { "amount": 9981519664, "target": { "key": "1f68514f97f013308cbd86f43b2a2cb70f933af2fc4c1a27cd19c9e95c2122e3" } } ], "extra": [ 1, 96, 141, 129, 251, 163, 153, 203, 5, 3, 179, 5, 85, 214, 30, 64, 22, 149, 11, 246, 77, 77, 153, 114, 176, 16, 227, 174, 143, 96, 244, 135, 254, 2, 17, 0, 0, 0, 13, 77, 161, 106, 58, 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