Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c1a3e3622a83f137e0d9f006c80b99722daa2405e6583f87aeaa5d27365ec75

Tx prefix hash: 4846214490d92201915ae845f503d834b2c0b7a6fb2ee81251697799cddcd0d7
Tx public key: 57fc7f79685f595ba710029697f9882ee5b291b6a0aa200c874eb5eea50c3286
Timestamp: 1723589446 Timestamp [UCT]: 2024-08-13 22:50:46 Age [y:d:h:m:s]: 00:246:07:25:25
Block: 1087310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175927 RingCT/type: yes/0
Extra: 0157fc7f79685f595ba710029697f9882ee5b291b6a0aa200c874eb5eea50c328602110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9e617e3b3e0eab918352f3d96649074490f25291e90d38d76b367318ccf4db9 0.600000000000 1561917 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": 1087320, "vin": [ { "gen": { "height": 1087310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9e617e3b3e0eab918352f3d96649074490f25291e90d38d76b367318ccf4db9" } } ], "extra": [ 1, 87, 252, 127, 121, 104, 95, 89, 91, 167, 16, 2, 150, 151, 249, 136, 46, 229, 178, 145, 182, 160, 170, 32, 12, 135, 78, 181, 238, 165, 12, 50, 134, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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