Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 211d09f22e30adb5830a282c7d537d3c4181e7210ac61ba5031967294200c738

Tx prefix hash: f63b643e794e977de2b95be30ffc4b936f91ea2bf0acf1423b53b99cba506b2b
Tx public key: 03e92ae9ea936446c33acc6e8f5359d06668433181a0d511053d8a413656f42b
Timestamp: 1602480907 Timestamp [UCT]: 2020-10-12 05:35:07 Age [y:d:h:m:s]: 04:075:13:54:57
Block: 140644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1042435 RingCT/type: yes/0
Extra: 0103e92ae9ea936446c33acc6e8f5359d06668433181a0d511053d8a413656f42b021100000194f4b4cc44000000000000000000

1 output(s) for total of 209.888550508000 dcy

stealth address amount amount idx
00: 9437d62cffe76bfe60440b459ae560f18e89e79686735814a14420db3a3bac6a 209.888550508000 233633 of 0

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": 140654, "vin": [ { "gen": { "height": 140644 } } ], "vout": [ { "amount": 209888550508, "target": { "key": "9437d62cffe76bfe60440b459ae560f18e89e79686735814a14420db3a3bac6a" } } ], "extra": [ 1, 3, 233, 42, 233, 234, 147, 100, 70, 195, 58, 204, 110, 143, 83, 89, 208, 102, 104, 67, 49, 129, 160, 213, 17, 5, 61, 138, 65, 54, 86, 244, 43, 2, 17, 0, 0, 1, 148, 244, 180, 204, 68, 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