Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63e7517985ffd20f086be7655314419b2d097101d3e7d08853278e50105e8924

Tx prefix hash: a716daf618f58c28c0c5444fb7fc73f381ecde3628ee6295a46f42a737cf4a8d
Tx public key: f854dd7ddd223ff1f337db3df069f88ccd9b429e21e20372a0d3e07e922e87b5
Timestamp: 1733873199 Timestamp [UCT]: 2024-12-10 23:26:39 Age [y:d:h:m:s]: 00:187:00:13:03
Block: 1172474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133385 RingCT/type: yes/0
Extra: 01f854dd7ddd223ff1f337db3df069f88ccd9b429e21e20372a0d3e07e922e87b50211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c878fe49ef7ca85626ea88c55370315b6eaae10542d4f7a9dbe40e796a394338 0.600000000000 1658371 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": 1172484, "vin": [ { "gen": { "height": 1172474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c878fe49ef7ca85626ea88c55370315b6eaae10542d4f7a9dbe40e796a394338" } } ], "extra": [ 1, 248, 84, 221, 125, 221, 34, 63, 241, 243, 55, 219, 61, 240, 105, 248, 140, 205, 155, 66, 158, 33, 226, 3, 114, 160, 211, 224, 126, 146, 46, 135, 181, 2, 17, 0, 0, 0, 6, 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