Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88853ae65d17d44748fa54ce99ead508b63cfd17792a3f638aede746fa8499ab

Tx prefix hash: b96e2cfe4290f8c1ecb24538b45f5fab1e97643b9c62263f4da7da050f1ee84a
Tx public key: aa02bc7a0c7c572f2d13dcafa3071b5bb81f83e84925f997b4832b3ddaa76a8f
Timestamp: 1726348817 Timestamp [UCT]: 2024-09-14 21:20:17 Age [y:d:h:m:s]: 00:212:16:58:15
Block: 1110182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151859 RingCT/type: yes/0
Extra: 01aa02bc7a0c7c572f2d13dcafa3071b5bb81f83e84925f997b4832b3ddaa76a8f021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9f6bf43fda768bb3cbad23ce783653a71e5a0e01abbbce591f188eba701d042 0.600000000000 1588699 of 15

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": 1110192, "vin": [ { "gen": { "height": 1110182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9f6bf43fda768bb3cbad23ce783653a71e5a0e01abbbce591f188eba701d042" } } ], "extra": [ 1, 170, 2, 188, 122, 12, 124, 87, 47, 45, 19, 220, 175, 163, 7, 27, 91, 184, 31, 131, 232, 73, 37, 249, 151, 180, 131, 43, 61, 218, 167, 106, 143, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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