Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b63b55778e16189a97bee5fa3ec1e8e1300a936e69ffcbfb57ae3ed313f62d0

Tx prefix hash: 230b4eb5bc9e16dca4ae3c78d45174fb093ce162493cd82a2745d6a6e176d1f5
Tx public key: 0b2356b3e0c39ea694ac3a178ba4ba85dc4452da96cfaa53c00b1446c91a575d
Timestamp: 1713096538 Timestamp [UCT]: 2024-04-14 12:08:58 Age [y:d:h:m:s]: 01:016:06:13:49
Block: 1000297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272596 RingCT/type: yes/0
Extra: 010b2356b3e0c39ea694ac3a178ba4ba85dc4452da96cfaa53c00b1446c91a575d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a99e8e4ae65fc66cd70591eb599b45f4908109ee2419119389ef235fd06c073f 0.600000000000 1460795 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": 1000307, "vin": [ { "gen": { "height": 1000297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a99e8e4ae65fc66cd70591eb599b45f4908109ee2419119389ef235fd06c073f" } } ], "extra": [ 1, 11, 35, 86, 179, 224, 195, 158, 166, 148, 172, 58, 23, 139, 164, 186, 133, 220, 68, 82, 218, 150, 207, 170, 83, 192, 11, 20, 70, 201, 26, 87, 93, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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