Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2343b2a273a99ecd4f061823b27c170a72b58660ea93f7093788bff4342fe662

Tx prefix hash: bea6c1d893a53bec4b6e8d8bad7125b7f0f839595cf1e8f7bdf78a2a22288bbb
Tx public key: 89d83f7c5f94b941ed1102fca743c875cb007e1359bcfa9f9f16b162da38078b
Timestamp: 1733865374 Timestamp [UCT]: 2024-12-10 21:16:14 Age [y:d:h:m:s]: 00:105:14:19:34
Block: 1172408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75236 RingCT/type: yes/0
Extra: 0189d83f7c5f94b941ed1102fca743c875cb007e1359bcfa9f9f16b162da38078b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3925f41d43946a7a6e61d76fe8c0fe1bbfa05312c8467790d543090d80dba836 0.600000000000 1658295 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": 1172418, "vin": [ { "gen": { "height": 1172408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3925f41d43946a7a6e61d76fe8c0fe1bbfa05312c8467790d543090d80dba836" } } ], "extra": [ 1, 137, 216, 63, 124, 95, 148, 185, 65, 237, 17, 2, 252, 167, 67, 200, 117, 203, 0, 126, 19, 89, 188, 250, 159, 159, 22, 177, 98, 218, 56, 7, 139, 2, 17, 0, 0, 0, 1, 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