Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45c67f711841190ca075bb9655c620a703faff4a7f7b30ce768770045686c8f6

Tx prefix hash: 008bf1c92c47406369a87f076355ae527d54bf637d711f046ccb7bcf7cee4d45
Tx public key: db8ca5f09930fd5b870192230ee599bd035c8c0a448ab854bc0d0ee99c7594e1
Timestamp: 1723568441 Timestamp [UCT]: 2024-08-13 17:00:41 Age [y:d:h:m:s]: 00:162:02:47:50
Block: 1087145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115917 RingCT/type: yes/0
Extra: 01db8ca5f09930fd5b870192230ee599bd035c8c0a448ab854bc0d0ee99c7594e102110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 120d7dc93b424509b73115931c3e278fb9a1a074d26ed8b3bd024e59a7e9bd80 0.600000000000 1561750 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": 1087155, "vin": [ { "gen": { "height": 1087145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "120d7dc93b424509b73115931c3e278fb9a1a074d26ed8b3bd024e59a7e9bd80" } } ], "extra": [ 1, 219, 140, 165, 240, 153, 48, 253, 91, 135, 1, 146, 35, 14, 229, 153, 189, 3, 92, 140, 10, 68, 138, 184, 84, 188, 13, 14, 233, 156, 117, 148, 225, 2, 17, 0, 0, 0, 6, 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