Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 002334e27fb2aed6df6122fdc91438c3b7eba9b5fb5274537b45868658a48e62

Tx prefix hash: 981b1dfd9c6c54996e3b28d03cbc82397ae57f821948872be4ffdf2f819efffc
Tx public key: 5a704f59480cb00ba791a4b791ec9004e212e2e656c685dc1df44d28d6b54cd2
Timestamp: 1698955489 Timestamp [UCT]: 2023-11-02 20:04:49 Age [y:d:h:m:s]: 01:193:01:28:14
Block: 883296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398996 RingCT/type: yes/0
Extra: 015a704f59480cb00ba791a4b791ec9004e212e2e656c685dc1df44d28d6b54cd202110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.726563683000 dcy

stealth address amount amount idx
00: b2fbf98245a89c2f3bb3b7afb875884b50b10497c88a266ff50594fa2d5ba106 0.726563683000 1338988 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": 883306, "vin": [ { "gen": { "height": 883296 } } ], "vout": [ { "amount": 726563683, "target": { "key": "b2fbf98245a89c2f3bb3b7afb875884b50b10497c88a266ff50594fa2d5ba106" } } ], "extra": [ 1, 90, 112, 79, 89, 72, 12, 176, 11, 167, 145, 164, 183, 145, 236, 144, 4, 226, 18, 226, 230, 86, 198, 133, 220, 29, 244, 77, 40, 214, 181, 76, 210, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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