Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b255b77df014e398ab15651af5b20ddc0e294e6e7757dada8235a6a0afc109a6

Tx prefix hash: 2aff5b46be8735282f8b9c7149206714e229794e018fdb68f945ea67ca8b1cab
Tx public key: 725801b0d37d75db425f8b22d4ae6e8031e809a7c480affdbf723bfd64e5d233
Timestamp: 1705589755 Timestamp [UCT]: 2024-01-18 14:55:55 Age [y:d:h:m:s]: 01:296:01:38:02
Block: 938067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470425 RingCT/type: yes/0
Extra: 01725801b0d37d75db425f8b22d4ae6e8031e809a7c480affdbf723bfd64e5d23302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd57354e11b83eeaccd3f98000e72e5141fd93acec039e1f97dea70ff28e7267 0.600000000000 1396131 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": 938077, "vin": [ { "gen": { "height": 938067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd57354e11b83eeaccd3f98000e72e5141fd93acec039e1f97dea70ff28e7267" } } ], "extra": [ 1, 114, 88, 1, 176, 211, 125, 117, 219, 66, 95, 139, 34, 212, 174, 110, 128, 49, 232, 9, 167, 196, 128, 175, 253, 191, 114, 59, 253, 100, 229, 210, 51, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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