Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9afa757970a035cac900770d70ef0b59b37cd8f5c32ac23074e151ff4937eaac

Tx prefix hash: 157cbb5da51f0ee9c8ea822aed677a6ea1251d9f1825e7649118fc939d4821d8
Tx public key: 7ebfbc22a4ab5d1bd78bed000a15d193e08ba6771472ae4dfc12d2c5a48da9ce
Timestamp: 1710525608 Timestamp [UCT]: 2024-03-15 18:00:08 Age [y:d:h:m:s]: 01:009:22:34:56
Block: 979022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268066 RingCT/type: yes/0
Extra: 017ebfbc22a4ab5d1bd78bed000a15d193e08ba6771472ae4dfc12d2c5a48da9ce02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc78bc13ecf7b32fbbecbaf4fc9b278773696cc03e3b5e8e97f136dfd9d8546d 0.600000000000 1439051 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": 979032, "vin": [ { "gen": { "height": 979022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc78bc13ecf7b32fbbecbaf4fc9b278773696cc03e3b5e8e97f136dfd9d8546d" } } ], "extra": [ 1, 126, 191, 188, 34, 164, 171, 93, 27, 215, 139, 237, 0, 10, 21, 209, 147, 224, 139, 166, 119, 20, 114, 174, 77, 252, 18, 210, 197, 164, 141, 169, 206, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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