Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66aa39b7354d41c0b2b1612bad9fd7a42d5ab02656c2907bd60070cf76f01ca0

Tx prefix hash: eb02943daa6493c05c0255231e66097ddf635ab03605dea78f3ae8bfdc7ad907
Tx public key: 6f5aa5e5bb33b4834a27770f76d74f5b28a2cb938ce180922c5a2f8428d9199b
Timestamp: 1579276807 Timestamp [UCT]: 2020-01-17 16:00:07 Age [y:d:h:m:s]: 05:292:21:38:06
Block: 47804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1357015 RingCT/type: yes/0
Extra: 016f5aa5e5bb33b4834a27770f76d74f5b28a2cb938ce180922c5a2f8428d9199b02110000000a4ac5aa02000000000000000000

1 output(s) for total of 426.193026929000 dcy

stealth address amount amount idx
00: 70e08497e29d585615d8cd8f4e4f1e6b6ed5e105b6dc71a2ef9cfd535c6076a3 426.193026929000 88257 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": 47814, "vin": [ { "gen": { "height": 47804 } } ], "vout": [ { "amount": 426193026929, "target": { "key": "70e08497e29d585615d8cd8f4e4f1e6b6ed5e105b6dc71a2ef9cfd535c6076a3" } } ], "extra": [ 1, 111, 90, 165, 229, 187, 51, 180, 131, 74, 39, 119, 15, 118, 215, 79, 91, 40, 162, 203, 147, 140, 225, 128, 146, 44, 90, 47, 132, 40, 217, 25, 155, 2, 17, 0, 0, 0, 10, 74, 197, 170, 2, 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