Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a916a16f63f45e143ba24f11c10055b24d1ad22907dc5084d50462b17b7f378

Tx prefix hash: 47a4506bb88b2d99f0cf67b7116da206a2319e33b31e1003f26e97e784c7dae5
Tx public key: 945e4360f7cce83a1a9a05f5482e6ffbbcde851a4c3bb83a5841d1e0a32f9d65
Timestamp: 1696642322 Timestamp [UCT]: 2023-10-07 01:32:02 Age [y:d:h:m:s]: 02:032:16:54:39
Block: 864112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542997 RingCT/type: yes/0
Extra: 01945e4360f7cce83a1a9a05f5482e6ffbbcde851a4c3bb83a5841d1e0a32f9d65021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.841081867000 dcy

stealth address amount amount idx
00: 69fdd7a2e7f03718c9a3ebf7221f89a0f9cf30189765aea1d7e7697c667b1503 0.841081867000 1318620 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": 864122, "vin": [ { "gen": { "height": 864112 } } ], "vout": [ { "amount": 841081867, "target": { "key": "69fdd7a2e7f03718c9a3ebf7221f89a0f9cf30189765aea1d7e7697c667b1503" } } ], "extra": [ 1, 148, 94, 67, 96, 247, 204, 232, 58, 26, 154, 5, 245, 72, 46, 111, 251, 188, 222, 133, 26, 76, 59, 184, 58, 88, 65, 209, 224, 163, 47, 157, 101, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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