Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14500d43907e5224f6c37e55af6e93a8bbe3d2570537a07ac172c90dfcd918a9

Tx prefix hash: bb00f91c2896fa8eba28faf14f9cf853c48b6ea7fc85524827d2b0dd1af0a085
Tx public key: 16d512d3caa40703333ca8ec27d7b5bba2814bf5ec206bf5a7b7b35d9ff743f8
Timestamp: 1636159887 Timestamp [UCT]: 2021-11-06 00:51:27 Age [y:d:h:m:s]: 03:364:02:56:34
Block: 368215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1036312 RingCT/type: yes/0
Extra: 0116d512d3caa40703333ca8ec27d7b5bba2814bf5ec206bf5a7b7b35d9ff743f802110000000b328bb496000000000000000000

1 output(s) for total of 36.978666732000 dcy

stealth address amount amount idx
00: b7fdfe34c89df513e7aa4ecd5f2d2d3105a6c2f4a2ce14fc79eea4a3fd3cd9e6 36.978666732000 746917 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": 368225, "vin": [ { "gen": { "height": 368215 } } ], "vout": [ { "amount": 36978666732, "target": { "key": "b7fdfe34c89df513e7aa4ecd5f2d2d3105a6c2f4a2ce14fc79eea4a3fd3cd9e6" } } ], "extra": [ 1, 22, 213, 18, 211, 202, 164, 7, 3, 51, 60, 168, 236, 39, 215, 181, 187, 162, 129, 75, 245, 236, 32, 107, 245, 167, 183, 179, 93, 159, 247, 67, 248, 2, 17, 0, 0, 0, 11, 50, 139, 180, 150, 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