Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0dbd28f64c03873ca7603e213fc6a9e310162b8de62e2f3886723e96c1c81b5

Tx prefix hash: bf7116748312e8430aa18f3f5d0d80d7d007c97df39f0d9925c34423412bc4c0
Tx public key: 991363d4e2cb2ca36934c08b46807d8d3cb467c4034bc1aac5d54c9aecc910a8
Timestamp: 1698225501 Timestamp [UCT]: 2023-10-25 09:18:21 Age [y:d:h:m:s]: 01:156:04:27:26
Block: 877246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372623 RingCT/type: yes/0
Extra: 01991363d4e2cb2ca36934c08b46807d8d3cb467c4034bc1aac5d54c9aecc910a802110000000533af99f4000000000000000000

1 output(s) for total of 0.760886461000 dcy

stealth address amount amount idx
00: 28c7cb91a471850378cefdca86ce934055e79a4cde5eeb98e16d39dd40122cfb 0.760886461000 1332614 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": 877256, "vin": [ { "gen": { "height": 877246 } } ], "vout": [ { "amount": 760886461, "target": { "key": "28c7cb91a471850378cefdca86ce934055e79a4cde5eeb98e16d39dd40122cfb" } } ], "extra": [ 1, 153, 19, 99, 212, 226, 203, 44, 163, 105, 52, 192, 139, 70, 128, 125, 141, 60, 180, 103, 196, 3, 75, 193, 170, 197, 213, 76, 154, 236, 201, 16, 168, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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