Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3933121781a792418153254ebbcd15dd7eb5076b5dc06448a217627d860d6d45

Tx prefix hash: bfa0b6b75b332fa5d6d0472dbb6a7441c49297cdd7b1e86cb08896ffe43d0044
Tx public key: fa44110bcb9209930298c5d4e8d20b4901258fe86bb3d86697d64fc6ed0a958b
Timestamp: 1731163276 Timestamp [UCT]: 2024-11-09 14:41:16 Age [y:d:h:m:s]: 00:159:10:08:51
Block: 1150026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113753 RingCT/type: yes/0
Extra: 01fa44110bcb9209930298c5d4e8d20b4901258fe86bb3d86697d64fc6ed0a958b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ead3bfc6e1aecac7cd05f5bff17748c1f3cc76c938dae0b497df0d1b73b988c 0.600000000000 1635219 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": 1150036, "vin": [ { "gen": { "height": 1150026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ead3bfc6e1aecac7cd05f5bff17748c1f3cc76c938dae0b497df0d1b73b988c" } } ], "extra": [ 1, 250, 68, 17, 11, 203, 146, 9, 147, 2, 152, 197, 212, 232, 210, 11, 73, 1, 37, 143, 232, 107, 179, 216, 102, 151, 214, 79, 198, 237, 10, 149, 139, 2, 17, 0, 0, 0, 4, 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