Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 434dd4652e96f3873a9db179e2c16b9221a27bbf452fbe638d424a97f6bc2e2e

Tx prefix hash: de699288704b7bd4e34677754e9cc61290badb4fee1f3879e1ef8bf5e82c1d04
Tx public key: eb8ab2239cc13b8c4eedbf2ebcf5e937d8b70769a67691057a1d7e132f3df624
Timestamp: 1731625230 Timestamp [UCT]: 2024-11-14 23:00:30 Age [y:d:h:m:s]: 00:167:16:28:13
Block: 1153842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119687 RingCT/type: yes/0
Extra: 01eb8ab2239cc13b8c4eedbf2ebcf5e937d8b70769a67691057a1d7e132f3df624021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35056918c75b6f33b3d5fdc214a0ab0a780eb190499e224c6abb25a22dbe5a26 0.600000000000 1639453 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": 1153852, "vin": [ { "gen": { "height": 1153842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35056918c75b6f33b3d5fdc214a0ab0a780eb190499e224c6abb25a22dbe5a26" } } ], "extra": [ 1, 235, 138, 178, 35, 156, 193, 59, 140, 78, 237, 191, 46, 188, 245, 233, 55, 216, 183, 7, 105, 166, 118, 145, 5, 122, 29, 126, 19, 47, 61, 246, 36, 2, 17, 0, 0, 0, 3, 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