Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ebe03286e471a6a3c4b1c0d65c5d4a3f6a70e83e33df786eaae9eead43afaad

Tx prefix hash: 0a919c68611b079e530df195fec8d5430956c2d35312132d7d2dab803cb26ab7
Tx public key: 32e252f70bb4c4a5c8b7d0125f8f84ee55c618d65625cd630e9b271cffdc2fd6
Timestamp: 1713258801 Timestamp [UCT]: 2024-04-16 09:13:21 Age [y:d:h:m:s]: 01:260:15:54:34
Block: 1001655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445034 RingCT/type: yes/0
Extra: 0132e252f70bb4c4a5c8b7d0125f8f84ee55c618d65625cd630e9b271cffdc2fd6021100000004679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc392169ad14b39c46f3cc3175a1dc775b107af60cbb93e9cf3f4018d854ee69 0.600000000000 1462163 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": 1001665, "vin": [ { "gen": { "height": 1001655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc392169ad14b39c46f3cc3175a1dc775b107af60cbb93e9cf3f4018d854ee69" } } ], "extra": [ 1, 50, 226, 82, 247, 11, 180, 196, 165, 200, 183, 208, 18, 95, 143, 132, 238, 85, 198, 24, 214, 86, 37, 205, 99, 14, 155, 39, 28, 255, 220, 47, 214, 2, 17, 0, 0, 0, 4, 103, 154, 138, 129, 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