Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 466f06f7a04751c64106402cfd9bcc4e25187c44c70ba1008c395dfa48445b0d

Tx prefix hash: 6520f2748a312b9893fe2c103bb21007d9b3b8f3b5414d8bf90029ee0866c108
Tx public key: 330e1fa47bf40facdeaef030df10e5e1d0ad34b78def6aa6ced84902dff531f9
Timestamp: 1585731365 Timestamp [UCT]: 2020-04-01 08:56:05 Age [y:d:h:m:s]: 04:294:20:26:57
Block: 90333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110877 RingCT/type: yes/0
Extra: 01330e1fa47bf40facdeaef030df10e5e1d0ad34b78def6aa6ced84902dff531f90211000002b660e3cc90000000000000000000

1 output(s) for total of 308.098828369000 dcy

stealth address amount amount idx
00: 4e4690632e37f0db5fa09bbf33a82678933cc22209624593d2a62c2d8f98ea16 308.098828369000 161893 of 0

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": 90343, "vin": [ { "gen": { "height": 90333 } } ], "vout": [ { "amount": 308098828369, "target": { "key": "4e4690632e37f0db5fa09bbf33a82678933cc22209624593d2a62c2d8f98ea16" } } ], "extra": [ 1, 51, 14, 31, 164, 123, 244, 15, 172, 222, 174, 240, 48, 223, 16, 229, 225, 208, 173, 52, 183, 141, 239, 106, 166, 206, 216, 73, 2, 223, 245, 49, 249, 2, 17, 0, 0, 2, 182, 96, 227, 204, 144, 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