Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e89b21bdb73254b123007144999af96a4b91fc24d5412dce6d2b5f488f70a09

Tx prefix hash: 634c81ccaa47e69e951948d8515fe32350d8cf8b3f1cfb6570735e5a68743a20
Tx public key: c9c04c0ea9bc09b12a401568b16a96fcc3ee94759e12c356893faf27e29d842d
Timestamp: 1730057661 Timestamp [UCT]: 2024-10-27 19:34:21 Age [y:d:h:m:s]: 00:145:12:38:09
Block: 1140899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103801 RingCT/type: yes/0
Extra: 01c9c04c0ea9bc09b12a401568b16a96fcc3ee94759e12c356893faf27e29d842d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ea1a0f8876a1b03b3524f6cc9b370a70416b27167ba0a20163df2688e29b5d8 0.600000000000 1624702 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": 1140909, "vin": [ { "gen": { "height": 1140899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea1a0f8876a1b03b3524f6cc9b370a70416b27167ba0a20163df2688e29b5d8" } } ], "extra": [ 1, 201, 192, 76, 14, 169, 188, 9, 177, 42, 64, 21, 104, 177, 106, 150, 252, 195, 238, 148, 117, 158, 18, 195, 86, 137, 63, 175, 39, 226, 157, 132, 45, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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