Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68ce13db097d852f6231267155bcf6e7c5df7d0b38ea5f9638d063ff0c4a35ba

Tx prefix hash: 4b1744ad236c8512936cdf1216391587b35c6d784bbd07cbfdd3ad18b01f09df
Tx public key: fbe6ea6736293bb3135ca095d6307b957d113ce8c10f68d4ca729f2ed3f72602
Timestamp: 1706875215 Timestamp [UCT]: 2024-02-02 12:00:15 Age [y:d:h:m:s]: 00:348:12:02:14
Block: 948740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249489 RingCT/type: yes/0
Extra: 01fbe6ea6736293bb3135ca095d6307b957d113ce8c10f68d4ca729f2ed3f7260202110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b75dc8930dfe08a92a3c2685021e859a0b6e9fbb9d9a8bb859be2aeab61ab253 0.600000000000 1407212 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": 948750, "vin": [ { "gen": { "height": 948740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b75dc8930dfe08a92a3c2685021e859a0b6e9fbb9d9a8bb859be2aeab61ab253" } } ], "extra": [ 1, 251, 230, 234, 103, 54, 41, 59, 179, 19, 92, 160, 149, 214, 48, 123, 149, 125, 17, 60, 232, 193, 15, 104, 212, 202, 114, 159, 46, 211, 247, 38, 2, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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