Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95c854331d91b2b6b8d05ecf666f88557171be2713f1f4fe0205071da59f1ef

Tx prefix hash: 543c9dc6b32c49d659fa31ca39b508818688d9fe4fe1e0245130b1c010705761
Tx public key: 7bb7fdc6c0503cdc1de66aad32940f6c4b2afcbd4877b9a2bcbea75fd1d24e22
Timestamp: 1726586616 Timestamp [UCT]: 2024-09-17 15:23:36 Age [y:d:h:m:s]: 01:108:14:34:20
Block: 1112156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336122 RingCT/type: yes/0
Extra: 017bb7fdc6c0503cdc1de66aad32940f6c4b2afcbd4877b9a2bcbea75fd1d24e2202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08f4773379b8e7956263be1646b566c5378b4ec777d4e9604084249eddcb315e 0.600000000000 1591377 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": 1112166, "vin": [ { "gen": { "height": 1112156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08f4773379b8e7956263be1646b566c5378b4ec777d4e9604084249eddcb315e" } } ], "extra": [ 1, 123, 183, 253, 198, 192, 80, 60, 220, 29, 230, 106, 173, 50, 148, 15, 108, 75, 42, 252, 189, 72, 119, 185, 162, 188, 190, 167, 95, 209, 210, 78, 34, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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