Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55e4696b95099e64de73270d30d12e9e53787f3804e303c6aec2b9d616f70c01

Tx prefix hash: a9d211bdf8474da16a920b43ad0a58e2fbbf0fed4a7f47103325edc3efd22f78
Tx public key: 10c2e92229146f5e39f2b9aafd89082935a6a8cdc74472f75c16e5f7117a9212
Timestamp: 1722446463 Timestamp [UCT]: 2024-07-31 17:21:03 Age [y:d:h:m:s]: 00:297:05:05:38
Block: 1077833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212361 RingCT/type: yes/0
Extra: 0110c2e92229146f5e39f2b9aafd89082935a6a8cdc74472f75c16e5f7117a921202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 177dff97619e23712472fe98a915ef553d15686680ae94c573b144b559d9e2fa 0.600000000000 1550388 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": 1077843, "vin": [ { "gen": { "height": 1077833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "177dff97619e23712472fe98a915ef553d15686680ae94c573b144b559d9e2fa" } } ], "extra": [ 1, 16, 194, 233, 34, 41, 20, 111, 94, 57, 242, 185, 170, 253, 137, 8, 41, 53, 166, 168, 205, 199, 68, 114, 247, 92, 22, 229, 247, 17, 122, 146, 18, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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