Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6b6c814ca5f80c7d477df26c9c90278865911faa19e8595337e6100e738f62e

Tx prefix hash: 243747b6ccf1d0a4b4eee5d4f1a219ac73482e6c90142c4a287c7ce143921a76
Tx public key: 5ecced302c52c41c858e312e3752735b29b62ddd1495a794b4b57332b3d1defb
Timestamp: 1696682464 Timestamp [UCT]: 2023-10-07 12:41:04 Age [y:d:h:m:s]: 01:188:07:09:22
Block: 864443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395621 RingCT/type: yes/0
Extra: 015ecced302c52c41c858e312e3752735b29b62ddd1495a794b4b57332b3d1defb02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.838960530000 dcy

stealth address amount amount idx
00: 4010ceae15ae3a9e1ab5e3a7b3c717461dc0fdbd8ec0aa6d8e47ac5490ea6e3c 0.838960530000 1318957 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": 864453, "vin": [ { "gen": { "height": 864443 } } ], "vout": [ { "amount": 838960530, "target": { "key": "4010ceae15ae3a9e1ab5e3a7b3c717461dc0fdbd8ec0aa6d8e47ac5490ea6e3c" } } ], "extra": [ 1, 94, 204, 237, 48, 44, 82, 196, 28, 133, 142, 49, 46, 55, 82, 115, 91, 41, 182, 45, 221, 20, 149, 167, 148, 180, 181, 115, 50, 179, 209, 222, 251, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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