Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 714190ae5db27c741eb9b3b326f645b5db11328f2254227405cd80241cde8ee7

Tx prefix hash: bc81b1bca65fc897d50df35604f719ded028fec9a630a40c7797b744d2cae3d5
Tx public key: c3a7f2cce5dc979c8fb4dda2528b602b7eec3800aaad5aeff0f4c91b61367c7e
Timestamp: 1700946073 Timestamp [UCT]: 2023-11-25 21:01:13 Age [y:d:h:m:s]: 01:175:16:04:39
Block: 899587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386754 RingCT/type: yes/0
Extra: 01c3a7f2cce5dc979c8fb4dda2528b602b7eec3800aaad5aeff0f4c91b61367c7e021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.641645003000 dcy

stealth address amount amount idx
00: 52a3a8e8b037f4586355680b255473b91db77d34e237ac7b2195ea2c2efbd965 0.641645003000 1356046 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": 899597, "vin": [ { "gen": { "height": 899587 } } ], "vout": [ { "amount": 641645003, "target": { "key": "52a3a8e8b037f4586355680b255473b91db77d34e237ac7b2195ea2c2efbd965" } } ], "extra": [ 1, 195, 167, 242, 204, 229, 220, 151, 156, 143, 180, 221, 162, 82, 139, 96, 43, 126, 236, 56, 0, 170, 173, 90, 239, 240, 244, 201, 27, 97, 54, 124, 126, 2, 17, 0, 0, 0, 3, 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