Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6df1ec5d09915a92b456816d60f8bdc603d43323589f4a67d4898419a2df1b1b

Tx prefix hash: 40328d4526cc39bf6b49933dcfe32dc1b390a51f2e2f179c8a755d66543f0202
Tx public key: 2dea7ce1f86168786126c3bfce23912d31db0fd957d57c7a545f5264fba4682f
Timestamp: 1732016237 Timestamp [UCT]: 2024-11-19 11:37:17 Age [y:d:h:m:s]: 00:139:06:04:37
Block: 1157087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99326 RingCT/type: yes/0
Extra: 012dea7ce1f86168786126c3bfce23912d31db0fd957d57c7a545f5264fba4682f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 105adc4b16b2f48507b4fef3cd7b1786d71bf5858ecef9205a119f454c44bd32 0.600000000000 1642710 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": 1157097, "vin": [ { "gen": { "height": 1157087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "105adc4b16b2f48507b4fef3cd7b1786d71bf5858ecef9205a119f454c44bd32" } } ], "extra": [ 1, 45, 234, 124, 225, 248, 97, 104, 120, 97, 38, 195, 191, 206, 35, 145, 45, 49, 219, 15, 217, 87, 213, 124, 122, 84, 95, 82, 100, 251, 164, 104, 47, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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