Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18a495b71019b616b16541f7f8c6444c0cdd5af609853d915bcb54b916d1d550

Tx prefix hash: bd300be828da353c5dabcf73dd1a28aff073b1966ca1cd49e75c4769aa049fc2
Tx public key: 737ae6a1382524cb245c2d1b9ed2bb011d3f512e5c27392418e3266429e40757
Timestamp: 1647606881 Timestamp [UCT]: 2022-03-18 12:34:41 Age [y:d:h:m:s]: 02:280:17:58:12
Block: 461105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720186 RingCT/type: yes/0
Extra: 01737ae6a1382524cb245c2d1b9ed2bb011d3f512e5c27392418e3266429e40757021100000005d3fcec30000000000000000000

1 output(s) for total of 18.204048492000 dcy

stealth address amount amount idx
00: 9f310f0c5aa8c038dac998562cdf42d72b3676fdd838f74353a88ec6a2b92e99 18.204048492000 878270 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": 461115, "vin": [ { "gen": { "height": 461105 } } ], "vout": [ { "amount": 18204048492, "target": { "key": "9f310f0c5aa8c038dac998562cdf42d72b3676fdd838f74353a88ec6a2b92e99" } } ], "extra": [ 1, 115, 122, 230, 161, 56, 37, 36, 203, 36, 92, 45, 27, 158, 210, 187, 1, 29, 63, 81, 46, 92, 39, 57, 36, 24, 227, 38, 100, 41, 228, 7, 87, 2, 17, 0, 0, 0, 5, 211, 252, 236, 48, 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