Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83ab28dc07bdcafb96e74265dd46f5f5e065ad345860808a1ff67aeb9c7b3256

Tx prefix hash: 6e93788f207a5a0165f12e7a0dc6549db805d140e3a51f28a8dee1c372f50d3d
Tx public key: bc62df1b12672aaee7bd6010f96ff9dde2a833d32479615752ced54e36618402
Timestamp: 1700836609 Timestamp [UCT]: 2023-11-24 14:36:49 Age [y:d:h:m:s]: 01:137:23:23:08
Block: 898677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359786 RingCT/type: yes/0
Extra: 01bc62df1b12672aaee7bd6010f96ff9dde2a833d32479615752ced54e36618402021100000008faf35c9c000000000000000000

1 output(s) for total of 0.646115301000 dcy

stealth address amount amount idx
00: 1cc05f8f9234e7ac893642879b2fca5e6df8461d1725971fac0dc5ef74ad0651 0.646115301000 1355106 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": 898687, "vin": [ { "gen": { "height": 898677 } } ], "vout": [ { "amount": 646115301, "target": { "key": "1cc05f8f9234e7ac893642879b2fca5e6df8461d1725971fac0dc5ef74ad0651" } } ], "extra": [ 1, 188, 98, 223, 27, 18, 103, 42, 174, 231, 189, 96, 16, 249, 111, 249, 221, 226, 168, 51, 211, 36, 121, 97, 87, 82, 206, 213, 78, 54, 97, 132, 2, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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