Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f0af89a29fd7737e480c7bd60a244c28bfd96d3ac91322f7d89472f85040be3

Tx prefix hash: f56d5dd909e7b2a4c1d9d1319239a02efdc092eb0434d065d47ebe2eb7a24d30
Tx public key: 39781775552f53f0729fef1c985230634b0ec917214c8fd0eb8d2949b1027e2d
Timestamp: 1673579570 Timestamp [UCT]: 2023-01-13 03:12:50 Age [y:d:h:m:s]: 02:047:12:35:03
Block: 673579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555601 RingCT/type: yes/0
Extra: 0139781775552f53f0729fef1c985230634b0ec917214c8fd0eb8d2949b1027e2d0211000000028b7b6602000000000000000000

1 output(s) for total of 3.598761859000 dcy

stealth address amount amount idx
00: da15533351434c3184c7970dbb7d44e8755e1f2e1a8b69a06ca02f0bfbedae6a 3.598761859000 1115194 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": 673589, "vin": [ { "gen": { "height": 673579 } } ], "vout": [ { "amount": 3598761859, "target": { "key": "da15533351434c3184c7970dbb7d44e8755e1f2e1a8b69a06ca02f0bfbedae6a" } } ], "extra": [ 1, 57, 120, 23, 117, 85, 47, 83, 240, 114, 159, 239, 28, 152, 82, 48, 99, 75, 14, 201, 23, 33, 76, 143, 208, 235, 141, 41, 73, 177, 2, 126, 45, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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