Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 185a94fa530fa69c578e94de180dc0fc7539c4eba3a7dcf898be69abf90d4c65

Tx prefix hash: 23fc501dea1ed55aa2b040ae6aba980451c176d7e2f92ab125ebe88f660323c3
Tx public key: c3c059aa70c18665a69a6175f4be355bf501161b28a903420e7a5efdf84577f7
Timestamp: 1732215607 Timestamp [UCT]: 2024-11-21 19:00:07 Age [y:d:h:m:s]: 00:161:23:34:20
Block: 1158728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115608 RingCT/type: yes/0
Extra: 01c3c059aa70c18665a69a6175f4be355bf501161b28a903420e7a5efdf84577f70211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ead674f29a17fb7fa82e24327b7d944fd0fbfd7e6bf503dacbd6fa5605aa024a 0.600000000000 1644357 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": 1158738, "vin": [ { "gen": { "height": 1158728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ead674f29a17fb7fa82e24327b7d944fd0fbfd7e6bf503dacbd6fa5605aa024a" } } ], "extra": [ 1, 195, 192, 89, 170, 112, 193, 134, 101, 166, 154, 97, 117, 244, 190, 53, 91, 245, 1, 22, 27, 40, 169, 3, 66, 14, 122, 94, 253, 248, 69, 119, 247, 2, 17, 0, 0, 0, 1, 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