Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1845433ffe0de56cea34b1e8b19d7e7755bafc328b2cb049fb8a1dde9fe78700

Tx prefix hash: 9e45be6697b17f5a4fca55d42a4fd41299c157d7a2ef51968b4e49561bfa9ede
Tx public key: 4f02900c7ee22536c9e9ed4cc7675f4711558a14c2e4d92b56a34a8035520b3c
Timestamp: 1583530587 Timestamp [UCT]: 2020-03-06 21:36:27 Age [y:d:h:m:s]: 04:252:13:00:08
Block: 77633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1075124 RingCT/type: yes/0
Extra: 014f02900c7ee22536c9e9ed4cc7675f4711558a14c2e4d92b56a34a8035520b3c0211000000118a2ee0d9000000000000000000

1 output(s) for total of 339.451658400000 dcy

stealth address amount amount idx
00: 0231cfd2b1ef14de82d3b18f0ba0d26442a41dc017e9a21fd4e4a230c231f1c0 339.451658400000 142782 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": 77643, "vin": [ { "gen": { "height": 77633 } } ], "vout": [ { "amount": 339451658400, "target": { "key": "0231cfd2b1ef14de82d3b18f0ba0d26442a41dc017e9a21fd4e4a230c231f1c0" } } ], "extra": [ 1, 79, 2, 144, 12, 126, 226, 37, 54, 201, 233, 237, 76, 199, 103, 95, 71, 17, 85, 138, 20, 194, 228, 217, 43, 86, 163, 74, 128, 53, 82, 11, 60, 2, 17, 0, 0, 0, 17, 138, 46, 224, 217, 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