Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4ac125735cb6a17d0b4914946fa07c62196c53af1aa535e08d891b4756cf553

Tx prefix hash: cf47803f4a91b712e5678e948d46f911d3e7511c73aee891f71d96d241489c60
Tx public key: a7dbcb46b8998e5d092510ea3741cfcf6774a164b1e3e5c25b566a8f051c14c1
Timestamp: 1590430993 Timestamp [UCT]: 2020-05-25 18:23:13 Age [y:d:h:m:s]: 05:008:03:51:39
Block: 103112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1192797 RingCT/type: yes/0
Extra: 01a7dbcb46b8998e5d092510ea3741cfcf6774a164b1e3e5c25b566a8f051c14c10211000002c04710461d000000000000000000

1 output(s) for total of 279.478174787000 dcy

stealth address amount amount idx
00: f73212088413cc569f8bb3cec65eebda3b67ea9697fdf6ee80368fdd1a4810b0 279.478174787000 180981 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": 103122, "vin": [ { "gen": { "height": 103112 } } ], "vout": [ { "amount": 279478174787, "target": { "key": "f73212088413cc569f8bb3cec65eebda3b67ea9697fdf6ee80368fdd1a4810b0" } } ], "extra": [ 1, 167, 219, 203, 70, 184, 153, 142, 93, 9, 37, 16, 234, 55, 65, 207, 207, 103, 116, 161, 100, 177, 227, 229, 194, 91, 86, 106, 143, 5, 28, 20, 193, 2, 17, 0, 0, 2, 192, 71, 16, 70, 29, 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