Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f63cf2779273d109ff1d6401e8c9b517f3ad244cf239a5252a18dc57a71de31f

Tx prefix hash: 8f68891d0276eb5cec34cc9e11fa9d401441f01b5bdacb7fc67f73659cc79677
Tx public key: d5fe250ce0e68f6bb2a29361a66c094012f2d650bcd5adc9ae7a2029862c7815
Timestamp: 1734321246 Timestamp [UCT]: 2024-12-16 03:54:06 Age [y:d:h:m:s]: 00:093:15:58:25
Block: 1176191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66730 RingCT/type: yes/0
Extra: 01d5fe250ce0e68f6bb2a29361a66c094012f2d650bcd5adc9ae7a2029862c78150211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 230f6864418ec8f97e987e482f51d43382e9749e2d5dcc0c3dfe0011fc2a93c7 0.600000000000 1662522 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": 1176201, "vin": [ { "gen": { "height": 1176191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "230f6864418ec8f97e987e482f51d43382e9749e2d5dcc0c3dfe0011fc2a93c7" } } ], "extra": [ 1, 213, 254, 37, 12, 224, 230, 143, 107, 178, 162, 147, 97, 166, 108, 9, 64, 18, 242, 214, 80, 188, 213, 173, 201, 174, 122, 32, 41, 134, 44, 120, 21, 2, 17, 0, 0, 0, 5, 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