Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9537350cc1753e23d5c278fea0e4553b68449565e54b52ecbd778cdf5e2c1b2e

Tx prefix hash: d46c3932ff15bf999523ce84fdb4e1b61712f33f20c5e3af960e726e23a574d6
Tx public key: 3baf5a86eedc948a3d1e315a729cc9cc0bf9b4e69a83686010320a8ac5ee8ce8
Timestamp: 1724491333 Timestamp [UCT]: 2024-08-24 09:22:13 Age [y:d:h:m:s]: 00:265:02:39:28
Block: 1094805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189344 RingCT/type: yes/0
Extra: 013baf5a86eedc948a3d1e315a729cc9cc0bf9b4e69a83686010320a8ac5ee8ce802110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6dcfe46610d9375866577f6f03b6af95a0482c28453adf6882c79cde0bd97cf 0.600000000000 1569926 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": 1094815, "vin": [ { "gen": { "height": 1094805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6dcfe46610d9375866577f6f03b6af95a0482c28453adf6882c79cde0bd97cf" } } ], "extra": [ 1, 59, 175, 90, 134, 238, 220, 148, 138, 61, 30, 49, 90, 114, 156, 201, 204, 11, 249, 180, 230, 154, 131, 104, 96, 16, 50, 10, 138, 197, 238, 140, 232, 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