Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6698a2e39b815efc3bbad6e71567e077f1a24ad06591297f66ad5a4aad1a9b28

Tx prefix hash: f7b24a8a9c677a261601b8df9f80f1f7d78be917696bf74bbc898b612ec49a5e
Tx public key: fe523bdf753148dde0f87d2bd8e4ace5447164fe3fe3b27f5945bff600e25966
Timestamp: 1608993282 Timestamp [UCT]: 2020-12-26 14:34:42 Age [y:d:h:m:s]: 03:328:18:15:04
Block: 169814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 987189 RingCT/type: yes/0
Extra: 01fe523bdf753148dde0f87d2bd8e4ace5447164fe3fe3b27f5945bff600e2596602110000000cf6643c68000000000000000000

1 output(s) for total of 168.016307091000 dcy

stealth address amount amount idx
00: fb8b2609ed05c54c3923e82af9f2e44b64b782f6744fa5c8719c033164f48a1d 168.016307091000 317541 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": 169824, "vin": [ { "gen": { "height": 169814 } } ], "vout": [ { "amount": 168016307091, "target": { "key": "fb8b2609ed05c54c3923e82af9f2e44b64b782f6744fa5c8719c033164f48a1d" } } ], "extra": [ 1, 254, 82, 59, 223, 117, 49, 72, 221, 224, 248, 125, 43, 216, 228, 172, 229, 68, 113, 100, 254, 63, 227, 178, 127, 89, 69, 191, 246, 0, 226, 89, 102, 2, 17, 0, 0, 0, 12, 246, 100, 60, 104, 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