Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a14c5bd2ad0610b5e131f4862ccfd18f2dfa4dbeb00f1c1d3755f1aa62170cb

Tx prefix hash: 4425bfeab102af44d52051fbde8a0b0ac166dcb64d7fe760bbe8a0ac68615cda
Tx public key: bf30c3aa4ef11b582eeb1d400e20f9cf1c31f82f63f9d7d930ee8df47e836a38
Timestamp: 1675092960 Timestamp [UCT]: 2023-01-30 15:36:00 Age [y:d:h:m:s]: 01:289:12:51:17
Block: 686126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467874 RingCT/type: yes/0
Extra: 01bf30c3aa4ef11b582eeb1d400e20f9cf1c31f82f63f9d7d930ee8df47e836a380211000000015029cbac000000000000000000

1 output(s) for total of 3.270240338000 dcy

stealth address amount amount idx
00: 824270d17baad77e656c202c1ec11b4181c961b6fcc65d85b8f8cbc9f84e3f8c 3.270240338000 1128591 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": 686136, "vin": [ { "gen": { "height": 686126 } } ], "vout": [ { "amount": 3270240338, "target": { "key": "824270d17baad77e656c202c1ec11b4181c961b6fcc65d85b8f8cbc9f84e3f8c" } } ], "extra": [ 1, 191, 48, 195, 170, 78, 241, 27, 88, 46, 235, 29, 64, 14, 32, 249, 207, 28, 49, 248, 47, 99, 249, 215, 217, 48, 238, 141, 244, 126, 131, 106, 56, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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