Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4989b3b5fb65c60808ba04ad84effeb2517a8d65a4da3e5cdfd7ebc932f3510d

Tx prefix hash: 08d1965be1fa1f7a1b8540a94c57fd54049aea6d354611d310feef40df74d3b0
Tx public key: e1f5452223b0e8f10ebb2a9f17ea84ed136c8f046c63459750bef1dbcba5602a
Timestamp: 1679836242 Timestamp [UCT]: 2023-03-26 13:10:42 Age [y:d:h:m:s]: 02:027:19:39:57
Block: 725485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541402 RingCT/type: yes/0
Extra: 01e1f5452223b0e8f10ebb2a9f17ea84ed136c8f046c63459750bef1dbcba5602a021100000004e6d27f9c000000000000000000

1 output(s) for total of 2.421959674000 dcy

stealth address amount amount idx
00: 033b51c29aaf7dffedb30d6c038f4beac2044ed8e05aae1bda5a2107a65b4958 2.421959674000 1170622 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": 725495, "vin": [ { "gen": { "height": 725485 } } ], "vout": [ { "amount": 2421959674, "target": { "key": "033b51c29aaf7dffedb30d6c038f4beac2044ed8e05aae1bda5a2107a65b4958" } } ], "extra": [ 1, 225, 245, 69, 34, 35, 176, 232, 241, 14, 187, 42, 159, 23, 234, 132, 237, 19, 108, 143, 4, 108, 99, 69, 151, 80, 190, 241, 219, 203, 165, 96, 42, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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