Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 790135da5bc610fc733705095ce5f1c4c4e68404b85284a7cc7c771607f99dad

Tx prefix hash: adbbc4694a02201ee44e07103c923c2448256e1dfe0e45226e41d277a2f92bcd
Tx public key: d4cb5c15a7cfeda3bd12728f11f4e0abad5875c8bf7bea155a8683e2af51d1e7
Timestamp: 1721109426 Timestamp [UCT]: 2024-07-16 05:57:06 Age [y:d:h:m:s]: 00:252:14:10:32
Block: 1066769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180420 RingCT/type: yes/0
Extra: 01d4cb5c15a7cfeda3bd12728f11f4e0abad5875c8bf7bea155a8683e2af51d1e7021100000015e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3effc12ae1f74870a7591748cc9c086e508f0b07397d8b1b22636a8f5864997 0.600000000000 1537436 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": 1066779, "vin": [ { "gen": { "height": 1066769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3effc12ae1f74870a7591748cc9c086e508f0b07397d8b1b22636a8f5864997" } } ], "extra": [ 1, 212, 203, 92, 21, 167, 207, 237, 163, 189, 18, 114, 143, 17, 244, 224, 171, 173, 88, 117, 200, 191, 123, 234, 21, 90, 134, 131, 226, 175, 81, 209, 231, 2, 17, 0, 0, 0, 21, 233, 20, 221, 21, 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