Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afdc35164e17d1026b5b7b1b141d799a79087cbf8a5cca9f83c45b94480b8424

Tx prefix hash: befbe39f037017ddca35cb0dbb97c64913717bc0b97c601766e10838cd9a2a59
Tx public key: e9ef7761d078862c5061212f129b74955fc7ae4c76d4ca7198958d0e920c06e3
Timestamp: 1736537948 Timestamp [UCT]: 2025-01-10 19:39:08 Age [y:d:h:m:s]: 00:077:05:45:39
Block: 1194522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54985 RingCT/type: yes/0
Extra: 01e9ef7761d078862c5061212f129b74955fc7ae4c76d4ca7198958d0e920c06e30211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3eee63b2fd4a0513c8e2efa09de6a36b929eeafa877fb7b8d255d45d85c0f1e3 0.600000000000 1681095 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": 1194532, "vin": [ { "gen": { "height": 1194522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3eee63b2fd4a0513c8e2efa09de6a36b929eeafa877fb7b8d255d45d85c0f1e3" } } ], "extra": [ 1, 233, 239, 119, 97, 208, 120, 134, 44, 80, 97, 33, 47, 18, 155, 116, 149, 95, 199, 174, 76, 118, 212, 202, 113, 152, 149, 141, 14, 146, 12, 6, 227, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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