Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 435d71cd9f637e3665f32180852179d60317085a81155b4304e319424ea52872

Tx prefix hash: a9b4b78a267a2e9633c9958d86efeca5a0327826a5cc0bca7a6ddab72d49d198
Tx public key: a8b13df7cfc577bd9f1ac6d07d2568ffdff8b25e381629e224ab906eb8e1e2c1
Timestamp: 1655135918 Timestamp [UCT]: 2022-06-13 15:58:38 Age [y:d:h:m:s]: 02:204:02:02:52
Block: 521629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 667123 RingCT/type: yes/0
Extra: 01a8b13df7cfc577bd9f1ac6d07d2568ffdff8b25e381629e224ab906eb8e1e2c10211000000012e6b1fd5000000000000000000

1 output(s) for total of 11.471672984000 dcy

stealth address amount amount idx
00: 33b5aefa131ee87e2a574b1d1e69443d53e5037b7c9c5e286d1744889ae64182 11.471672984000 949536 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": 521639, "vin": [ { "gen": { "height": 521629 } } ], "vout": [ { "amount": 11471672984, "target": { "key": "33b5aefa131ee87e2a574b1d1e69443d53e5037b7c9c5e286d1744889ae64182" } } ], "extra": [ 1, 168, 177, 61, 247, 207, 197, 119, 189, 159, 26, 198, 208, 125, 37, 104, 255, 223, 248, 178, 94, 56, 22, 41, 226, 36, 171, 144, 110, 184, 225, 226, 193, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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