Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 396afb208a4a9e0f03949d337aa465f89ef1b8ec1ca5eb24e9d250d663a556a7

Tx prefix hash: d491a7dcffcf515aab77e43d2bdd207359405f72f34a243ecfeee626f601859b
Tx public key: 7c02a3b410efd2a73d10f27ac5a4fbcb0f26dcb126ad7b957ad091e78d1fda6f
Timestamp: 1711714685 Timestamp [UCT]: 2024-03-29 12:18:05 Age [y:d:h:m:s]: 01:222:19:51:14
Block: 988888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417918 RingCT/type: yes/0
Extra: 017c02a3b410efd2a73d10f27ac5a4fbcb0f26dcb126ad7b957ad091e78d1fda6f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc93502b51c835ea5a5428fdc6e5226329c4cc01e018beef6b4cd4ca3432d474 0.600000000000 1449175 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": 988898, "vin": [ { "gen": { "height": 988888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc93502b51c835ea5a5428fdc6e5226329c4cc01e018beef6b4cd4ca3432d474" } } ], "extra": [ 1, 124, 2, 163, 180, 16, 239, 210, 167, 61, 16, 242, 122, 197, 164, 251, 203, 15, 38, 220, 177, 38, 173, 123, 149, 122, 208, 145, 231, 141, 31, 218, 111, 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