Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbd458e84505bad680137e43ec45ffd8de218321d7c4c6ff57cc4f01f654bdd2

Tx prefix hash: f9ff0de2ab7db677a54fe458cb7056e3a0d48d01a6569f0e1ee587eaed2ee42e
Tx public key: 35e733674e25cff54ed1afdee9c6b7e2d1eca7a4cb6ed4cf747c50e3d64a39ff
Timestamp: 1705099249 Timestamp [UCT]: 2024-01-12 22:40:49 Age [y:d:h:m:s]: 01:088:07:31:48
Block: 934007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324222 RingCT/type: yes/0
Extra: 0135e733674e25cff54ed1afdee9c6b7e2d1eca7a4cb6ed4cf747c50e3d64a39ff02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c81ad814639ba14b5cd5e15448b9bc08f663d87b5c346f7b809c8bbf15f4f28a 0.600000000000 1391991 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": 934017, "vin": [ { "gen": { "height": 934007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c81ad814639ba14b5cd5e15448b9bc08f663d87b5c346f7b809c8bbf15f4f28a" } } ], "extra": [ 1, 53, 231, 51, 103, 78, 37, 207, 245, 78, 209, 175, 222, 233, 198, 183, 226, 209, 236, 167, 164, 203, 110, 212, 207, 116, 124, 80, 227, 214, 74, 57, 255, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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