Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0df98db835e0001c68405fdcd8b36d5e4a91da3f756f12e64065ebfd771fc0

Tx prefix hash: 73b2dfc5ca25cea92db28b6777e0de72d89e59ee394bacc9c40bca2ce76c8c0d
Tx public key: d13731739a977d1c7d221d963178bf6920f6e565f77984fff96ef50de243a9ae
Timestamp: 1634505995 Timestamp [UCT]: 2021-10-17 21:26:35 Age [y:d:h:m:s]: 03:071:04:56:10
Block: 355156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 828829 RingCT/type: yes/0
Extra: 01d13731739a977d1c7d221d963178bf6920f6e565f77984fff96ef50de243a9ae021100000001a272b9cb000000000000000000

1 output(s) for total of 40.852736776000 dcy

stealth address amount amount idx
00: 707e491ef037665ce2b74c2c536e35b0a9654af74ef64af348741a1fe7ce8496 40.852736776000 725202 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": 355166, "vin": [ { "gen": { "height": 355156 } } ], "vout": [ { "amount": 40852736776, "target": { "key": "707e491ef037665ce2b74c2c536e35b0a9654af74ef64af348741a1fe7ce8496" } } ], "extra": [ 1, 209, 55, 49, 115, 154, 151, 125, 28, 125, 34, 29, 150, 49, 120, 191, 105, 32, 246, 229, 101, 247, 121, 132, 255, 249, 110, 245, 13, 226, 67, 169, 174, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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