Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79efdd0c55b30be27238d2e114bc3d141c9500eddbb5b5b8e189154d47cc36bb

Tx prefix hash: c878d84da59609619fc08e95001aa831fdd9a1b1d48a9ec08114de9903d0279d
Tx public key: 6a5e8e3f50adf5a745e08523b03d43cb7f56723797702b25f24a59aa89b1681c
Timestamp: 1703022434 Timestamp [UCT]: 2023-12-19 21:47:14 Age [y:d:h:m:s]: 01:103:00:28:47
Block: 916807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334746 RingCT/type: yes/0
Extra: 016a5e8e3f50adf5a745e08523b03d43cb7f56723797702b25f24a59aa89b1681c021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21a481df96a78c78205f937e46ef70dd02f771828fa85f787197c9831cf8bb40 0.600000000000 1374367 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": 916817, "vin": [ { "gen": { "height": 916807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21a481df96a78c78205f937e46ef70dd02f771828fa85f787197c9831cf8bb40" } } ], "extra": [ 1, 106, 94, 142, 63, 80, 173, 245, 167, 69, 224, 133, 35, 176, 61, 67, 203, 127, 86, 114, 55, 151, 112, 43, 37, 242, 74, 89, 170, 137, 177, 104, 28, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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