Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3742cb3c60780687e99d918d1adc8e252a31ef5196ed0bc536eee10279fb70f0

Tx prefix hash: 0b8e0b14ce161c171b9feb05f8263a26d74a3b8dde3c0a97d11629ba24267edc
Tx public key: cb66492b9456c4e3ff933a26e667d672f3af70478a6634a28964aa9446fff1a6
Timestamp: 1719957414 Timestamp [UCT]: 2024-07-02 21:56:54 Age [y:d:h:m:s]: 01:132:23:08:19
Block: 1057196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353568 RingCT/type: yes/0
Extra: 01cb66492b9456c4e3ff933a26e667d672f3af70478a6634a28964aa9446fff1a60211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00f0f3e1842b8b490da5094e55d1735291c6e5f8265fe7794d76eaf332d475ac 0.600000000000 1527629 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": 1057206, "vin": [ { "gen": { "height": 1057196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00f0f3e1842b8b490da5094e55d1735291c6e5f8265fe7794d76eaf332d475ac" } } ], "extra": [ 1, 203, 102, 73, 43, 148, 86, 196, 227, 255, 147, 58, 38, 230, 103, 214, 114, 243, 175, 112, 71, 138, 102, 52, 162, 137, 100, 170, 148, 70, 255, 241, 166, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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