Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e668d4f748d20bf2b70768b9c5ac6c923ee040915e85e816c41d33ae48712ef7

Tx prefix hash: 832f2a704da153230208934985282ec7fae56210cc34f4d61e68a0d9dd5fe577
Tx public key: 00250883c270a52e1ecdca25d8ccb1dd205f87629036152ed2b79fffb2f5b63f
Timestamp: 1730130465 Timestamp [UCT]: 2024-10-28 15:47:45 Age [y:d:h:m:s]: 00:153:18:31:35
Block: 1141471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109723 RingCT/type: yes/0
Extra: 0100250883c270a52e1ecdca25d8ccb1dd205f87629036152ed2b79fffb2f5b63f02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85412a1ac819df2efcf05134b9da5a8b3d672f8e191ce2b5f607d11451e6ce6e 0.600000000000 1625278 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": 1141481, "vin": [ { "gen": { "height": 1141471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85412a1ac819df2efcf05134b9da5a8b3d672f8e191ce2b5f607d11451e6ce6e" } } ], "extra": [ 1, 0, 37, 8, 131, 194, 112, 165, 46, 30, 205, 202, 37, 216, 204, 177, 221, 32, 95, 135, 98, 144, 54, 21, 46, 210, 183, 159, 255, 178, 245, 182, 63, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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