Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a42d875209653b1b36adf73fac6fad5ba45f4114075ea24516d5dbb953b4267

Tx prefix hash: 1f1e543d4c470031584c34b170941d22edc9824bb2f2859835369b8eb3b4dc5b
Tx public key: b0a970d33233d3f1dfc22c80ad9527bce9c0a074767729b2d1c8892c93ee0bf4
Timestamp: 1730594042 Timestamp [UCT]: 2024-11-03 00:34:02 Age [y:d:h:m:s]: 00:137:17:15:41
Block: 1145291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98289 RingCT/type: yes/0
Extra: 01b0a970d33233d3f1dfc22c80ad9527bce9c0a074767729b2d1c8892c93ee0bf40211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bdc55815f36097fcf0e5cbca7297703e7d5ac6f4fda66f9377c05bd4fc03ac4 0.600000000000 1629700 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": 1145301, "vin": [ { "gen": { "height": 1145291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bdc55815f36097fcf0e5cbca7297703e7d5ac6f4fda66f9377c05bd4fc03ac4" } } ], "extra": [ 1, 176, 169, 112, 211, 50, 51, 211, 241, 223, 194, 44, 128, 173, 149, 39, 188, 233, 192, 160, 116, 118, 119, 41, 178, 209, 200, 137, 44, 147, 238, 11, 244, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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