Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea1ff043ec136461ff58675311984a29d75f7a1a0011f43071da4fc1cc2674db

Tx prefix hash: 350f7fe0a64368a23455bc1d64d0163eef91b492c146cb78acdcfaa70afd5e54
Tx public key: 3a1c61ea52bb8b7f4b5f704024ec9446b6df22f1a8da54c411b8d0fde8bfcb5e
Timestamp: 1577774278 Timestamp [UCT]: 2019-12-31 06:37:58 Age [y:d:h:m:s]: 05:041:11:07:58
Block: 35517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179438 RingCT/type: yes/0
Extra: 013a1c61ea52bb8b7f4b5f704024ec9446b6df22f1a8da54c411b8d0fde8bfcb5e021100000006d81c26c0000000000000000000

1 output(s) for total of 468.078064600000 dcy

stealth address amount amount idx
00: 45df840db6c90cb3e4437cc308af7cf8592c08baa19cdcf5a93d5acf9f5cff6b 468.078064600000 59933 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": 35527, "vin": [ { "gen": { "height": 35517 } } ], "vout": [ { "amount": 468078064600, "target": { "key": "45df840db6c90cb3e4437cc308af7cf8592c08baa19cdcf5a93d5acf9f5cff6b" } } ], "extra": [ 1, 58, 28, 97, 234, 82, 187, 139, 127, 75, 95, 112, 64, 36, 236, 148, 70, 182, 223, 34, 241, 168, 218, 84, 196, 17, 184, 208, 253, 232, 191, 203, 94, 2, 17, 0, 0, 0, 6, 216, 28, 38, 192, 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