Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf37c26335bdfc72b3e4777111c0d8613703b1050536da42b7dd380b140bf7b0

Tx prefix hash: 9a8c668bd7365fb6e6b83107984bbc899d543af029fc4b62b0717306caf4b45f
Tx public key: 0c3e53fc1c0779f6c66a6aba02ed2b3107af2bbe647699a18a4ed614de5f2ae6
Timestamp: 1726954570 Timestamp [UCT]: 2024-09-21 21:36:10 Age [y:d:h:m:s]: 00:173:18:26:47
Block: 1115216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124016 RingCT/type: yes/0
Extra: 010c3e53fc1c0779f6c66a6aba02ed2b3107af2bbe647699a18a4ed614de5f2ae6021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8beb96fcd62654342dfa291489a60c22357a1e3f19448951e91f3f7bf5d021d3 0.600000000000 1595271 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": 1115226, "vin": [ { "gen": { "height": 1115216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8beb96fcd62654342dfa291489a60c22357a1e3f19448951e91f3f7bf5d021d3" } } ], "extra": [ 1, 12, 62, 83, 252, 28, 7, 121, 246, 198, 106, 106, 186, 2, 237, 43, 49, 7, 175, 43, 190, 100, 118, 153, 161, 138, 78, 214, 20, 222, 95, 42, 230, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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